-
Notifications
You must be signed in to change notification settings - Fork 124
Issues: WICG/focus-visible
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[Bug] focusVisible status is not added correctly when user interacts with keyboard and mouse
#278
opened Mar 13, 2023 by
233mawile
Memory leaks when applyFocusVisiblePolyfill is applied then the element is removed
#273
opened Nov 15, 2022 by
ryuran
:focus-visible
should match when focus is programmatically moved to inside a dialog
#268
opened Apr 13, 2022 by
craigkovatch
Applying :focus-visible state after programmatically moving focus only on initial page landing
#266
opened Mar 12, 2022 by
domkl14
:focus-visible's "hidden focus" artifact can result in user UI confusion on Mac
#257
opened May 18, 2021 by
cookiecrook
[performance] applying the polyfill in self contained web components with light dom
#254
opened Apr 20, 2021 by
tlouisse
Always applies focus-visible to inputs in React even when click
#251
opened Mar 31, 2021 by
sklawren
Is there a way to remove the .focus-visible class name when clicking.
#236
opened Aug 24, 2020 by
kevzlou7979
Alternative approach that does not require adding a class / data attribute to the element
#211
opened Oct 11, 2019 by
airtable-JayRansijn
Closing a dialog by Escape key is also being considered as keyboard navigation
#183
opened Sep 18, 2018 by
saschanaz
Update explainer heuristic. Consider ignoring meta, alt/option, control keys.
#167
opened Aug 7, 2018 by
robdodson
2 of 4 tasks
Previous Next
ProTip!
no:milestone will show everything without a milestone.