From 6552691f7d8f979dd63f7721fc5baa3d870a17d2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alberto=20Bl=C3=A1zquez?= Date: Mon, 14 Jul 2025 14:36:34 +0200 Subject: [PATCH] Polish MultiSelectFilter appearance in Rules page (#227676) ## Summary Polish inner border in `` component, rendered upon clicking on `` in the Rule page. [Link to EuiSelectable docs](https://eui.elastic.co/docs/components/forms/selection/selectable/#the-basics). ### Screenshots
Before Screenshot 2025-07-11 at 16 44 06 Screenshot 2025-07-11 at 16 44 17
After Screenshot 2025-07-11 at 16 43 25 Screenshot 2025-07-11 at 16 43 34
### Checklist - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [x] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Only risk is we're keeping style overrides in EUI components, which should happen as little as possible. But the override enhances the appearance when putting these components together, which is an edge case. (cherry picked from commit f9424c700cbc34c2b6d7885cc6863841c0af3c86) --- .../public/common/component/multi_select_filter.tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/x-pack/solutions/security/plugins/cloud_security_posture/public/common/component/multi_select_filter.tsx b/x-pack/solutions/security/plugins/cloud_security_posture/public/common/component/multi_select_filter.tsx index fa78d705ed2cc..388bb30bb62c7 100644 --- a/x-pack/solutions/security/plugins/cloud_security_posture/public/common/component/multi_select_filter.tsx +++ b/x-pack/solutions/security/plugins/cloud_security_posture/public/common/component/multi_select_filter.tsx @@ -158,7 +158,7 @@ export const MultiSelectFilter = ({ compressed: false, 'data-test-subj': `${id}-search-input`, css: css` - border-radius: 0px !important; + box-shadow: none; `, }} emptyMessage={'empty'}