Repository navigation
Forward nested history events to same-origin iframe WindowProxy - #901
Merged
wieslawsoltes merged 1 commit intoSep 21, 2026
Conversation
wieslawsoltes
added this pull request to stack #902
September 21, 2026 07:36
This was referenced Sep 21, 2026
This was referenced Sep 21, 2026
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.
Fixes #898. The inner iframe updates its history URL/state after back/forward, but owner-registered
contentWindowlisteners never receivepopstateorhashchange. Deliver events once to the stable same-origin proxy with the correct state, URL pair, target and order; bound and release listeners, keep cross-origin DOM masked, and avoid creating an owner document for an opaque proxy. A fresh cached document may fulfill the fourth cross-document navigation without another network request.Top of native GitHub stack #902: #899 → #900 → #901. On macOS native Release,
iframe-navigation-lifecyclepasses 100 cycles plus opaque/cross-origin denial and 1 MiB update p95 3.63 ms with flat 1,849,528-byte heap.iframe-cross-origin-parent-message,history-same-documentand 20-cyclequery-iframe-worker-bootstrappass (p95 145.27 ms, flat heap). Evidence:docs/validation/iframe-url-history-896-898.md. Merge the stack after related Linux native, portable V8 and metadata runners pass; consolidation #76 remains open.Stack created with GitHub Stacks CLI • Give Feedback 💬