-
Notifications
You must be signed in to change notification settings - Fork 249
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
Radio inputs - fix arrow button functionality #1049
base: main
Are you sure you want to change the base?
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit cd07f09:
|
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.
Thanks for taking the time to contribute to this library ❤️
Co-authored-by: Philipp Fritsche <[email protected]>
@ph-fritsche Please let me know if I should do anything to address the failing linting job. I would volunteer to make the fixes, but the issues are all in files that this PR didn't change. If it helps in debugging, I get these linting issues when running Thanks! |
@ph-fritsche @vgpena I'm willing to work on this. If there is something I can do to push this forward just let me know |
Any update for this? I want the bug to be fixed, so I would create another PR if you don't finish this. |
Just saw this PR, looks like it's the same as the implementation I had, but I added an additional test to ensure that aria-disabled was still selectable. Happy for either fix to go through, but would be great to an eye on one of these from a maintainer. Is there anything blocking this particular PR at this point? |
@ph-fritsche Is there anything blocking this PR still? Would be happy to make any edits, looks like this is just blocked on maintainer review. |
What:
This PR fixes a bug where keyboard navigation through radio inputs did not work as expected (#1048).
Why:
This gives us true-to-life outputs when radio inputs are tested with the keyboard.
How:
keydown.ts
to send the correct directions for Down and Up key events.radio.ts
so that we only move forwards or backwards by 1 valid radio input.Checklist: