Skip to content

Conversation

@zcorpan
Copy link
Member

@zcorpan zcorpan commented Oct 16, 2025

Fixes #11797.

(See WHATWG Working Mode: Changes for more details.)


/nav-history-apis.html ( diff )

zcorpan added a commit to web-platform-tests/wpt that referenced this pull request Oct 16, 2025
zcorpan added a commit to web-platform-tests/wpt that referenced this pull request Oct 16, 2025
then return null.</p></li>

<li><p>If the <span>entry global object</span>'s <span data-x="window bc">browsing
context</span> is null, then return null.</p></li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is entry correct here (and below) or should it be this's relevant global object? (Which would require us to pass this.)

For instance, say a click handler in the parent stores iframe.contentWindow as childWindow, then calls iframe.remove(), and then calls childWindow.open(), this says that should work, right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to write multiple-globals tests to check this.

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Window open steps and destroyed navigables

2 participants