Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

popstate transitioning between documents may not be interoperable #4488

Open
domenic opened this issue Mar 29, 2019 · 0 comments
Open

popstate transitioning between documents may not be interoperable #4488

domenic opened this issue Mar 29, 2019 · 0 comments
Labels
interop Implementations are not interoperable with each other topic: document lifecycle topic: history

Comments

@domenic
Copy link
Member

domenic commented Mar 29, 2019

Porting from https://www.w3.org/Bugs/Public/show_bug.cgi?id=27188. This investigated scenarios like

navigating multiple steps backwards or forwards in history (e.g. history.go(-2)) between different documents. This lets you navigate to a session entry that's not its document's "latest entry", in which case, per current specification, a popstate event should be fired in addition to the pageshow that is fired.

The conclusion there seemed to be that the current spec for when to fire popstate is roughly correct and that there may be browser bugs.

(Note that popstate has some other issues e.g. #1042 and #1792.)

We should write web platform tests covering those cases and confirm the spec is reasonable. Ideally it would match at least some browsers; if not we may want to reconsider the tradeoff between what browsers want (expressed in that bug to be equal to the current spec) and what they actually do.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
interop Implementations are not interoperable with each other topic: document lifecycle topic: history
2 participants
@domenic @annevk