Repository navigation
fix: navigate exact reference controls with bounded focus agreement - #700
Merged
Merged
Conversation
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
1 participant
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.
The native reference journey can tab away from its intended control while AT-SPI catches up, and forward-only traversal takes a whole-page loop when the target precedes the current control. Use genuine Shift+Tab for an earlier unique direct target, hold matching DOM focus while polling AT-SPI, reject a late returned success, and revalidate DOM before Return. Document focus loss after entering the group during that navigation call refuses activation.
Validation: all 27 focused inert controls passed against the exact observer source, including the three retained control-order sequences, delayed and late AT-SPI cases, fresh activation identity and original failures. Owner cleanup was observed empty with no escapes or post-pin failures. The reusable workflow is byte-identical. Native journey, timing and log-volume improvement remain unproven; the original run38138070411 log-budget failure and historical custody unknowns remain preserved. Synchronous AT-SPI calls remain bounded by the overall owner deadline.
Architecture map unaffected: navigation stays inside the existing observer and introduces no public API, dependency or process.