-
Notifications
You must be signed in to change notification settings - Fork 933
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
Handle End and Home Keys in list navigation #646
Conversation
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! 👍 I love this.
Ah, looks like we're just shy of our coverage threshold. Could you give that a look please? |
sure, will take a look tomorrow and come back to you. Thanks for the feedback! |
I updated a unit test to check that navigation keys (up, down, home, end) do nothing if list is empty. It should maintain the coverage now. You can check :) |
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.
Fantastic. Thank you!
Hey @silviuavram, would you be at all interested in being a primary maintainer of the project? Of everyone I feel really comfortable handing this project to you. See #647 |
🎉 This PR is included in version 3.1.11 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Hello Kent,
Thank you very much for your considering me. It will be both a pleasure and
a challenge to maintain and improve the project.
We are using it currently in our own project, Stardust UI Library, and I am
planning to contribute more to Downshift, as we are finding use cases that
need to be handled and it's way better to improve the source rather than
fixing stuff at our end. It will also be valuable for everyone using the
library.
If you agree to go forward with your decision, I will kindly ask for all
the information you consider necessary and good for me to know. I will also
sync with people from my organisation that have strong knowledge of project
ownership, but your help will also be very valuable.
I look forward to hearing from you.
Best regards,
Silviu
…On Tue, Jan 8, 2019 at 9:00 PM Kent C. Dodds ***@***.***> wrote:
🎉 This PR is included in version 3.1.11 🎉
The release is available on:
- npm package ***@***.*** dist-tag)
- GitHub release
<https://github.com/paypal/downshift/releases/tag/v3.1.11>
Your *semantic-release
<https://github.com/semantic-release/semantic-release>* bot 📦🚀
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#646 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AKwMgKstnYUV0xfXNztBK2Ks_qim42fSks5vBPjJgaJpZM4ZzvzM>
.
|
Sounds awesome! Could you shoot me an email and we'll chat about what needs to happen for this to work :) kent@doddsfamily.us |
What:
This PR aims to improve kb navigation inside the listbox by adding support for
Home
andEnd
. These keys should highlight first / last element, if the listbox is visible.Why:
Improves the component by adding another ARIA specification regarding kb navigation.
How:
Added event listeners for keydown on both
Home
andEnd
, and added handlers for each, in which I've used variations for thesetHighlightedIndex
function. Also added event names for both kets.Also added UTs for these changes, and planning to add E2E Cypress tests too. These are already written, however Cypress does not support Home and End at the moment. I've created a PR for implementing this in their repo here. Those tests are currently commented.
Checklist: