-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade EUI to v75.0.0 #150787
Upgrade EUI to v75.0.0 #150787
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Defend Workflows changes look good
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: cc @1Copenut |
Pinging @elastic/eui-design (EUI) |
Pinging @elastic/uptime (Team:uptime) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@elastic/security-defend-workflows changes LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uptime chagnes LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes to KeyboardShortcutsDoc
flyout LGTM for @elastic/kibana-presentation 👍
## Summary `eui@74.0.2` ⏩ `eui@75.0.0` ___ ## [`75.0.0`](https://github.com/elastic/eui/tree/v75.0.0) - `EuiFlyout`s now automatically shard all fixed `EuiHeader`s on the page. This means that interactions (mouse & keyboard) with items inside `EuiHeader`s when flyouts are open will no longer trigger focus fighting ([elastic#6566](elastic/eui#6566)) - `EuiFlyout`s now read out detailed screen reader dialog instructions and hints on open ([elastic#6566](elastic/eui#6566)) **Bug fixes** - Fixed `EuiSelectable` options with incorrect `aria-posinset` indices when rendered with group labels not at the start of the array ([elastic#6571](elastic/eui#6571)) - Fixed a bug with `EuiSearchBar` where filters with `multiSelect: false` were not able to select a new option when an option was already selected ([elastic#6577](elastic/eui#6577)) **Breaking changes** - Removed the ability to customize the `role` prop of `EuiFlyout`s. `EuiFlyout`s should always be dialog roles for screen reader consistency. ([elastic#6566](elastic/eui#6566)) - Removed `closeButtonAriaLabel` prop from `EuiFlyout` - use `closeButtonProps['aria-label']` instead ([elastic#6566](elastic/eui#6566)) --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
**Relates to:** #151244 ## Summary Re-enable `Do not clears kql when navigating to a new page` url state e2e test. ## Details Investigation has shown that #150787 lead to breaking this test. While it's not clear from the EUI upgrade PR itself the cause lays under the hood. It fixes retrieving the state (current KQL) from the url. As the test visits the page with the saved KQL which is properly restored the next `kqlSearch()` command types the same KQL in the query bar leading to invalid KQL and broken test eventually. For some reason the KQL wasn't able to restore on this page while it's not an issue anymore I removed `kqlSearch()` command and fixed the test this way.
…52075) **Relates to:** elastic#151244 ## Summary Re-enable `Do not clears kql when navigating to a new page` url state e2e test. ## Details Investigation has shown that elastic#150787 lead to breaking this test. While it's not clear from the EUI upgrade PR itself the cause lays under the hood. It fixes retrieving the state (current KQL) from the url. As the test visits the page with the saved KQL which is properly restored the next `kqlSearch()` command types the same KQL in the query bar leading to invalid KQL and broken test eventually. For some reason the KQL wasn't able to restore on this page while it's not an issue anymore I removed `kqlSearch()` command and fixed the test this way. (cherry picked from commit 5514f93)
…2075) (#152423) # Backport This will backport the following commits from `main` to `8.7`: - [[Security Solution] Re-enable a skipped url state e2e test (#152075)](#152075) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2023-03-01T09:04:31Z","message":"[Security Solution] Re-enable a skipped url state e2e test (#152075)\n\n**Relates to:** https://github.com/elastic/kibana/pull/151244\r\n\r\n## Summary\r\n\r\nRe-enable `Do not clears kql when navigating to a new page` url state e2e test.\r\n\r\n## Details\r\n\r\nInvestigation has shown that #150787 lead to breaking this test. While it's not clear from the EUI upgrade PR itself the cause lays under the hood. It fixes retrieving the state (current KQL) from the url. As the test visits the page with the saved KQL which is properly restored the next `kqlSearch()` command types the same KQL in the query bar leading to invalid KQL and broken test eventually. For some reason the KQL wasn't able to restore on this page while it's not an issue anymore I removed `kqlSearch()` command and fixed the test this way.","sha":"5514f93fc8ecccc007d1e25c9413df1c739feae9","branchLabelMapping":{"^v8.8.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rules","backport:prev-minor","v8.7.0","v8.8.0"],"number":152075,"url":"https://github.com/elastic/kibana/pull/152075","mergeCommit":{"message":"[Security Solution] Re-enable a skipped url state e2e test (#152075)\n\n**Relates to:** https://github.com/elastic/kibana/pull/151244\r\n\r\n## Summary\r\n\r\nRe-enable `Do not clears kql when navigating to a new page` url state e2e test.\r\n\r\n## Details\r\n\r\nInvestigation has shown that #150787 lead to breaking this test. While it's not clear from the EUI upgrade PR itself the cause lays under the hood. It fixes retrieving the state (current KQL) from the url. As the test visits the page with the saved KQL which is properly restored the next `kqlSearch()` command types the same KQL in the query bar leading to invalid KQL and broken test eventually. For some reason the KQL wasn't able to restore on this page while it's not an issue anymore I removed `kqlSearch()` command and fixed the test this way.","sha":"5514f93fc8ecccc007d1e25c9413df1c739feae9"}},"sourceBranch":"main","suggestedTargetBranches":["8.7"],"targetPullRequestStates":[{"branch":"8.7","label":"v8.7.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.8.0","labelRegex":"^v8.8.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/152075","number":152075,"mergeCommit":{"message":"[Security Solution] Re-enable a skipped url state e2e test (#152075)\n\n**Relates to:** https://github.com/elastic/kibana/pull/151244\r\n\r\n## Summary\r\n\r\nRe-enable `Do not clears kql when navigating to a new page` url state e2e test.\r\n\r\n## Details\r\n\r\nInvestigation has shown that #150787 lead to breaking this test. While it's not clear from the EUI upgrade PR itself the cause lays under the hood. It fixes retrieving the state (current KQL) from the url. As the test visits the page with the saved KQL which is properly restored the next `kqlSearch()` command types the same KQL in the query bar leading to invalid KQL and broken test eventually. For some reason the KQL wasn't able to restore on this page while it's not an issue anymore I removed `kqlSearch()` command and fixed the test this way.","sha":"5514f93fc8ecccc007d1e25c9413df1c739feae9"}}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
…52075) **Relates to:** elastic#151244 ## Summary Re-enable `Do not clears kql when navigating to a new page` url state e2e test. ## Details Investigation has shown that elastic#150787 lead to breaking this test. While it's not clear from the EUI upgrade PR itself the cause lays under the hood. It fixes retrieving the state (current KQL) from the url. As the test visits the page with the saved KQL which is properly restored the next `kqlSearch()` command types the same KQL in the query bar leading to invalid KQL and broken test eventually. For some reason the KQL wasn't able to restore on this page while it's not an issue anymore I removed `kqlSearch()` command and fixed the test this way.
Summary
eui@74.0.2
⏩eui@75.0.0
75.0.0
EuiFlyout
s now automatically shard all fixedEuiHeader
s on the page. This means that interactions (mouse & keyboard) with items insideEuiHeader
s when flyouts are open will no longer trigger focus fighting (#6566)EuiFlyout
s now read out detailed screen reader dialog instructions and hints on open (#6566)Bug fixes
EuiSelectable
options with incorrectaria-posinset
indices when rendered with group labels not at the start of the array (#6571)EuiSearchBar
where filters withmultiSelect: false
were not able to select a new option when an option was already selected (#6577)Breaking changes
role
prop ofEuiFlyout
s.EuiFlyout
s should always be dialog roles for screen reader consistency. (#6566)closeButtonAriaLabel
prop fromEuiFlyout
- usecloseButtonProps['aria-label']
instead (#6566)