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

[Security:Assets:Endpoints:Event Filters page]Activating buttons do nothing #206043

Open
L1nBra opened this issue Jan 9, 2025 · 2 comments
Open
Labels
defect-level-2 Serious UX disruption with workaround impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Project:Accessibility Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. WCAG A

Comments

@L1nBra
Copy link

L1nBra commented Jan 9, 2025

Description
When user activates buttons some change on the page should happen or new page, dialog/flyout should open. In case user has to fill something in order to be able to activate them, information about it should be presented for the user or at least buttons should be inactive.

Preconditions
Security -> Assets -> Endpoints -> Event Filters page.

Steps to reproduce

1.Navigate to Add Event Filter button.
2.Press Enter.
3.Navigate to AND button.
4.Press Enter.
5.Navigate to Add nested condition button.
6.Press Enter.
7.Observe the page.

Screen recording
https://github.com/user-attachments/assets/ad4d7a0f-ae60-426c-9ef4-fbe7e26a865d

UI elements
Image

Actual Result

  • When user press Enter or clicks on buttons - nothing happens.

Expected Result

  • Corresponding action should happen or information, text should be presented visually and announced for the user if some conditions are not met for buttons to take action.

Notes:
When user fills row above these buttons and then press Enter on AND, Add nested condition - additional rows appear.

Meta Issue

Kibana Version: 8.17.0-SNAPSHOT

OS: Windows 11 Pro

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

WCAG or Vendor Guidance (optional)

Related to: https://github.com/elastic/kibana-team/issues/1280

@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 9, 2025
@L1nBra L1nBra added WCAG A impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. defect-level-2 Serious UX disruption with workaround labels Jan 9, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 9, 2025
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:high Addressing this issue will have a high level of impact on the quality/strength of our product. Project:Accessibility Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. WCAG A
Projects
None yet
Development

No branches or pull requests

2 participants