-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Security Solution] Timeline bar on the rules table page causes broken focus #152344
Comments
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
@MadameSheema @michaelolo24 I've noticed this behavior, please triage. |
Hey @maximpn this has always been disabled on the rules table page, but something may have changed recently in this file or the path name for that page may have changed to cause this issue: https://github.com/elastic/kibana/blob/main/x-pack/plugins/security_solution/public/common/utils/timeline/use_show_timeline_for_path.ts We'll get a fix in, thanks! |
@machadoum or @semd , quick question. Should the rules table page, if so, @maximpn it might involve adding
hideTimeline: true flag added
|
I believe the timeline started appearing on the rules page when the tabs were introduced to the URL. So to make it work as expected, we have to configure the new links here. I would also update the |
@maximpn looks like this behavior no longer appears on main, and I saw that the tests are re-enabled. Could you confirm this is fixed? |
@christineweng I've checked this problem on main and it's not fixed. I had to add As far as I see rule search bar isn't focusable from the first click (as you can see on the video below). This is the main problem as Screen.Recording.2023-05-24.at.12.47.58.movBut it works as expected when I removed the timeline bar by removing this code block (as you can see on the video below). Screen.Recording.2023-05-24.at.12.48.48.movA similar search bar field on the Shared Exception Lists page works fine (gets focused by clicking once) as the page doesn't contain the timeline bar. I also noticed that |
… issue, causing focus issues (#158392) ## Summary This pr removes some code added 2 years ago to work around an eui issue with the global search bar and timeline focus, was causing issues in some cases, like in #152344 none of this code is needed, as the original bug no longer exists. ### Checklist - [x] [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 - [x] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/)) Co-authored-by: Kibana Machine <[email protected]>
…s tests (#158560) **Relates to:** #152344, #152470 **Depends on:** #158392 ## Summary Removes `force` option from Cypress actions like `type()`, `click()` and etc. It helps to catch UI quirks instead of silently ignoring them. ## Details After merging back of #158392 it's possible to remove `force: true` flag from the Cypress actions used in Detection rules tests. Based on the discussion in #152470 it's bette to avoid forced actions and leave a comment if there is no other way than forcing an action.
This bug was fixed by #158392, closing it. |
Relates to: #151244
Description
EUI team worked on improving accessibility and with EUI v75.0.0 release focus is handling another way. After that upgrade we encountered a problem of failing tests in
main
and had to skip failing tests. Later investigation and consultation with EUI team revealed that we have anEuiFlyout
shown at the rules table (see a screenshot).One can see
Add Integrations
button becomes focused after a page reload andbody
element has a classeuiBody--hasFlyout
. Such behavior causes e2e tests failing since Cypress tries typing in a field but focus gets transferred to another element.The timeline bar's implementation should be changed to avoid displaying an
EuiFlyout
which causes the problem.The text was updated successfully, but these errors were encountered: