-
Notifications
You must be signed in to change notification settings - Fork 28
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
feat: add keyboard navigation to attributions and signals lists #2583
Conversation
037c64d
to
84f2f8b
Compare
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.
Cool. Sometimes using arrow keys is a bit slow (still less that 0.5s but its noticeable). For example, if you're on the second-last item and press down, it takes a while for the highlighted item to move.
4abb826
to
bcf883d
Compare
84f2f8b
to
a6c9ea0
Compare
bcf883d
to
dca49c0
Compare
a6c9ea0
to
065f2d9
Compare
049dc28
to
4be36e9
Compare
065f2d9
to
7ca8c19
Compare
ae99e47
to
fbf99e6
Compare
7ca8c19
to
45258c4
Compare
fbf99e6
to
359aa5e
Compare
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.
Hey, finally figured out that a bug I'm encountering in the follow-up already exists in this version.
To reproduce:
- Select a resource without attributions
- Focus on the attributions panel, eg. by clicking on the scrollbar
- Scroll down using the down arrow
- Select a different resource without attributions
- Focus on the attributions panel, eg. by clicking on the scrollbar
- Scroll down using the down arrow
Notice that the focused index was preserved from the previous list.
e49bc07
to
2ec903d
Compare
45258c4
to
9edb3b3
Compare
I think I found a pretty simple solution to this issue that should also help you with the focus-stealing problems you faced in your follow-up task. |
9edb3b3
to
9563b34
Compare
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.
It's still a little buggy:
- Click on a resource with no attached attributions
- Click on an attribution
- Click on a resource with an attached attribution
- Click on a resource with no attached attributions
Notice that the focus index from step 2 was preserved.
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.
Seems to work, I'm just praying that I never have to open up use-virtuoso-refs.ts
again.
9c8afb8
to
ebd09c6
Compare
c9b54aa
to
a0de24d
Compare
ebd09c6
to
3f7f9f4
Compare
72eb751
to
7c556e9
Compare
2b34713
to
109cd84
Compare
99140be
to
f2c7fc3
Compare
109cd84
to
b95ffda
Compare
f2c7fc3
to
0c6d8c5
Compare
b95ffda
to
18d42f1
Compare
3c02b80
to
d26f86d
Compare
18d42f1
to
29cd131
Compare
d26f86d
to
d0c56c4
Compare
- merge PackageCard and ListCard components - track keyboard selected item in list and grouped-list - add focus styling to package card closes #971 Signed-off-by: Maxim Stykow <maxim.stykow@tngtech.com>
29cd131
to
50a0462
Compare
- keep track of focused ID instead of focused index in Virtuoso - add focus state for tree nodes and define keyboard actions closes #2572 Signed-off-by: Maxim Stykow <maxim.stykow@tngtech.com> Signed-off-by: Markus Obendrauf <markus.obendrauf@tngtech.com>
feat: add keyboard navigation for resource tree
Summary of changes
Context and reason for change
closes #971
How can the changes be tested
Check keyboard navigation after clicking on a package card in the attributions or signals lists. Pay special attention also to switching tabs: the previously focused package card should not carry over to another tab.