-
Notifications
You must be signed in to change notification settings - Fork 21
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
Feature request: Focus management #33
Comments
@hugogiraudel Tnx :) Maybe an optional feature might be the way to go? Here's an example pattern from W3C WAI-ARIA |
Hi there, My two cents: I think it's a good idea as an option. The most common way to use a toggle is that hidden content follows the trigger (DOM speaking). This way, appearing content becomes next content in the flow — and if any focusable element inside, it naturally appears in the focus flow too. But if for any reason the toggled content is anywhere else in the DOM, I think it's better to move focus to the toggled content (same arguments than with the dialog pattern) as recommended by @joe-watkins. |
Hi. Sorry, I am not a bigger help right now. But this would be the number one feature addition I would love to see! :) |
Hello :) Great work here!
I'd like to recommend the idea of focus management for your plugin. It would look something like this:
tabindex="-1"
to target so it can receive focus.What ya think?
The text was updated successfully, but these errors were encountered: