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

Treeview component guidance considerations and issues #3298

Open
mbgower opened this issue Dec 2, 2022 · 0 comments
Open

Treeview component guidance considerations and issues #3298

mbgower opened this issue Dec 2, 2022 · 0 comments

Comments

@mbgower
Copy link
Contributor

mbgower commented Dec 2, 2022

This discussion summarizes considerations and issues identified with the Treeview component which were not regarded as important enough to warrant a bug issue. More details and context can be found in the Treeview usage and Style PDFs (which contain comments from both Jess and me).

  1. in what situations are treeviews NOT alphabetical at each hierarchy? The Products folder in the screenshot in the Overview section of the Usage is jumbled alphabetically. If alphabetical is the default, that should be included in the Usage guidance. If there are cases where it is not, those should be explained.
  2. for overflow content, the full name should be exposed on hover and focus
  3. The Space key should be added to the keyboard controls table under Interactions as "Selects a node."
  4. Resolve how to deal with icons in regard to exposing the icon name as part of the node.
  5. The style page is missing several common states, including Selected+focused.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Later 🧊
Development

No branches or pull requests

3 participants