Skip to content

Conversation

@domenic
Copy link
Member

@domenic domenic commented Apr 10, 2025

Closes #11199.

As discussed there, there are deeper issues around whether a History object is associated with a Window vs. History object, and how that intersects with #3267 around Window object reuse.

However, in the meantime, this makes the traversal from History → Document consistent with the rest of the specification, and stops using the undefined concept of "history's associated Document".


/nav-history-apis.html ( diff )

Closes #11199.

As discussed there, there are deeper issues around whether a History object is associated with a Window vs. History object, and how that intersects with #3267 around Window object reuse.

However, in the meantime, this makes the traversal from History → Document consistent with the rest of the specification, and stops using the undefined concept of "history's associated Document".
@domenic domenic merged commit dba6e7b into main Apr 10, 2025
2 checks passed
@domenic domenic deleted the history-document branch April 10, 2025 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

Shared history push/replace state steps access "associated Document" of history

3 participants