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

[Discover][KEYBOARD]: Would we consider adding a Select all / Deselect all control to the available fields for Discover? #121452

Open
Tracked by #85965
1Copenut opened this issue Dec 16, 2021 · 3 comments
Labels
Feature:Discover Discover Application impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:needs-research This issue requires some research before it can be worked on or estimated Project:Accessibility Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.

Comments

@1Copenut
Copy link
Contributor

Describe the feature:
While auditing the Discover data grid feature for keyboard navigation and accessibility, I had to press TAB and ENTER a high number of times to build dense data grids with multiple columns. I found myself wondering if a Select all and Deselect all control might make sense for this UI.

Describe a specific use case for the feature:

  • I have created a data grid with a high number of columns, say 15. Instead of having to press the red X buttons to remove each column, I could press Deselect all and go back to a default data grid.
  • I want a data grid with most of the available columns. I could select all with one click, then click 3-5 remove X buttons instead of clicking to add each column.

Screen Shot 2021-12-16 at 2 18 43 PM

@1Copenut 1Copenut added Feature:Discover Discover Application Project:Accessibility Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. labels Dec 16, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@elasticmachine
Copy link
Contributor

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

@kertal
Copy link
Member

kertal commented Dec 17, 2021

I think a Deselect all would make sense ... however given that we usually have a large number of fields, I would hesitate offering a Select all button because of the possible performance impact

@KOTungseth KOTungseth added loe:needs-research This issue requires some research before it can be worked on or estimated impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Discover Discover Application impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:needs-research This issue requires some research before it can be worked on or estimated Project:Accessibility Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
Projects
None yet
Development

No branches or pull requests

4 participants