-
Notifications
You must be signed in to change notification settings - Fork 80
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
fix(button-group): handle keyboard focus for async menu buttons #1142
Conversation
Thank you, 🤖 Clarity Release Bot |
a5b6132
to
4507b45
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.
LGTM
With both synchronous and asynchronous population, focus is moved to the first menu button when the button group menu is opened, keyboard focus works properly, and the menu is closed when one of the menu buttons is activated. CDE-1571 closes #952
🎉 This PR is included in version 16.3.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Hi there 👋, this is an automated message. To help Clarity keep track of discussions, we automatically lock closed PRs after 14 days. Please look for another open issue or open a new issue with updated details and reference this one as necessary. |
PR Checklist
PR Type
Bugfix
What is the current behavior?
If button group menu buttons are populated asynchronously, focus is not handled properly and the menu is not closed when one of the menu buttons is activated.
Issue Number: #952, CDE-1571
What is the new behavior?
With both synchronous and asynchronous population, focus is moved to the first menu button when the button group menu is opened, keyboard focus works properly, and the menu is closed when one of the menu buttons is activated.
Does this PR introduce a breaking change?
No