Repository navigation
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 37912007-07c2-40e4-81bd-df708aa99fe2
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Check the live
isDefaultflag before expensive focusability geometry when finding a default element. Unmarked candidates cannot be the answer, so they do not need those reads.This is a live predicate reorder, not a cache or traversal rewrite. Visibility/accessibility checks still run for actual default candidates, and live property changes remain observable.
Evidence chain
Implicated stacks during unresponsive renderer
Public Mover,
findDefaultand context/virtual-parent traversal establish the search context. The dominant context/traversal work is not reduced by this change; no entire-workload or renderer-unresponsive causal claim is made.Baseline result
5 / 94 / 662.Geometry API reads can be cached browser work. They are not forced-layout counts or measured production CPU savings.
Scope and limits