Skip to content
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

[Search:WebCrawlers:ViewCrawler:Extraction rules page]Content disappears from page when navigating only with keyboard from bottom to top in Add content field rule flyout #199181

Closed
L1nBra opened this issue Nov 6, 2024 · 5 comments
Assignees
Labels
defect-level-2 Serious UX disruption with workaround impact:critical This issue should be addressed immediately due to a critical level of impact on the product. Project:Accessibility Team:Search WCAG A

Comments

@L1nBra
Copy link

L1nBra commented Nov 6, 2024

Description
Content shouldn't disappear from the page when only navigating through elements inside the flyout.

Preconditions
Stateful Web crawlers -> View Crawler -> Manage Domains page, Extraction rules tab is opened.
Domain is added.

Steps to reproduce

1.Navigate to Add content field rule button by pressing Tab key.
2.Press Enter.
3.Navigate to Cancel button while pressing Tab key.
4.Navigate to Field name by pressing Shift + Tab keys.
5.Observe the page.

Actual Result

  • When navigating with only keyboard by pressing Shift + Tab keys - content from the page disappears.

Expected Result

  • Content doesn't disappear from the page.

Meta Issue

Kibana Version: 8.17.0-SNAPSHOT

OS: Windows 11 Pro

Browser: Chrome Version 130.0.6723.70 (Official Build) (64-bit)

WCAG or Vendor Guidance (optional)

Related to: https://github.com/elastic/search-team/issues/8256

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-accessibility (Project:Accessibility)

@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 6, 2024
@L1nBra L1nBra added WCAG A impact:critical This issue should be addressed immediately due to a critical level of impact on the product. Team:Search defect-level-2 Serious UX disruption with workaround labels Nov 6, 2024
@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 6, 2024
@navarone-feekery
Copy link
Contributor

This happens when navigating forward using the Tab key as well.
The point of failure is always in the same spot; between the Extracted value and A fixed value radio buttons.

@navarone-feekery
Copy link
Contributor

Console error:

Detected an unhandled Promise rejection.

        Message: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7Btype%2C%20message%2C%20ref%7D for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

I expect that the radio has some sort of "on blur" effect that is expecting a value to exist.

@navarone-feekery navarone-feekery self-assigned this Nov 20, 2024
@navarone-feekery
Copy link
Contributor

This was resolved by @jedrazb in #201191
(Thanks!)

@navarone-feekery
Copy link
Contributor

Evidence of fix:

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect-level-2 Serious UX disruption with workaround impact:critical This issue should be addressed immediately due to a critical level of impact on the product. Project:Accessibility Team:Search WCAG A
Projects
None yet
Development

No branches or pull requests

5 participants