Skip to content

Route keyboard focus across nested webviews - #527

Merged
wieslawsoltes merged 1 commit into
mainfrom
feature/nested-keyboard-focus-526
Sep 19, 2026
Merged

wieslawsoltes merged 1 commit into
mainfrom
feature/nested-keyboard-focus-526

Conversation

@wieslawsoltes

Copy link
Copy Markdown
Collaborator

Native keyboard dispatch selected the top-level realm when an unchanged Code OSS webview focused its child window with BODY active, and sequential focus order could not cross the iframe boundary. This routes BODY-focused keyboard events through the tracked child context and computes Tab order over the unified document tree, including forward entry, exit, reverse return, and cancellation.

Authored regression sources cover the Code-shaped trusted Ctrl+F fields and browser/native cross-frame traversal. Only git diff --check ran under the current implementation-first policy; execution, positive-tabindex/empty-frame edge cases, lifecycle, performance, accessibility, package, and unchanged-product evidence remain deferred in #268.

Closes #526
Progresses #268

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Route keyboard focus and Tab traversal across nested webviews

1 participant