-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Improve performance of focus selectors in v9 #24183
Comments
Blocked by: microsoft/keyborg#19 |
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
The current
data-keyboard-nav
selector that is applied to the FluentProvider causes too much style recalclation each time the user's navigation mode changes (mouse/keyboard).Below are results of the
SelectorStats
trace fromedge://tracing
which measures the time spent per-selector during the matching phase. The comparison was done by comparing selector stats for.fui-focus-visible
(polyfill) vs the current[data-keyboard-nav]
selector.(Lower numbers are better)
[data-keyboard-nav]
on provider rootTasks
.fui-FluentProvider
does not need to be in the selector at allCSS.supports("selector(:focus-visible)")
to check platform support and default to:focus-visible
feat: use browser:focus-visible
if supported #24195The text was updated successfully, but these errors were encountered: