-
Notifications
You must be signed in to change notification settings - Fork 6.8k
feat(aria/tree): create tree behavior #32569
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
Open
wagnermaciel
wants to merge
14
commits into
angular:main
Choose a base branch
from
wagnermaciel:aria-menu
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1,452
−451
Open
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
385da11
feat(multiple): add subset support to list nav
wagnermaciel 37589ec
feat(multiple): add focusable attr to list items
wagnermaciel 92d4b5a
feat(multiple): add Tree behavior
wagnermaciel 8bf1daa
refactor(aria/tree): switch list for tree behavior
wagnermaciel 6ac0c18
refactor(aria/tree): visible item focus management
wagnermaciel c5e2921
refactor(aria/tree): rename allItems to items
wagnermaciel ed1c999
refactor(aria/tree): simplify expansion logic
wagnermaciel 144f26b
fix(multiple): linted and unit tests
wagnermaciel 25a2e15
fix(multiple): update aria api goldens
wagnermaciel 976d06c
Revert "feat(multiple): add focusable attr to list items"
wagnermaciel 4a5275a
refactor(aria/tree): simplify visible item focus management
wagnermaciel e023b1a
fix(aria/tree): small perf optimization to _peek
wagnermaciel 71f1c42
fix(aria/tree): linted
wagnermaciel 8022526
fix(aria/tree): updated api goldens
wagnermaciel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The items override feels a bit weird, because whether an override is provided or not, the moving index is always based on the
activeIndexfrom the original input, and the following case becomes hard to reason out.This last part is implicit and not easy to observe.
This makes me think about maybe
ListNavigationbehavior should just be a set of utility methods, and each method always take all necessary informations (items, activeIndex, wrap, etc.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think
ListNavigationshould be a set of utility methods since it would require a lot of args in order to perform its operations. Either way, this is outside the scope of this PR.This strange behavior can be replicated by changing the
inputs.itemscurrently. We could prevent this misuse of the behavior with some strict checks that warn or error if these come up. I think we are over-anticipating future concerns that I'm not convinced we will actually encounter