Repository navigation
Traverse nested cross-document history - #594
Merged
Merged
Conversation
This was referenced Sep 19, 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.
Closes #593. Advances #267 and #264.
Traverse bounded per-frame cross-document history through the established lifecycle while preserving stable WindowProxy/reflected-src behavior, restoring entry state, ordering traversal events and retiring outgoing work. Joint top-level history and bfcache remain explicit deferrals.
WPT-shaped/native contracts document the boundary.
git diff --checkpassed; authored contracts and runtime gates were not executed under the current implementation-throughput policy.