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.

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

Should document.open really change the URL but leave the serialized state? #4285

Closed

bzbarsky opened this issue Jan 11, 2019 · 2 comments

Labels

topic: document.open()

Contributor

bzbarsky commented Jan 11, 2019

https://html.spec.whatwg.org/multipage/dynamic-markup-insertion.html#document-open-steps step 11 calls https://html.spec.whatwg.org/multipage/history.html#url-and-history-update-steps without a serialized state. Per https://html.spec.whatwg.org/multipage/history.html#url-and-history-update-steps step 3, that will keep the existing serialized state, if any, but use the new URL. This doesn't make much sense to me, honestly: the state is tied to the URL in typical uses of the state, no?

What do UAs actually implement here?

@domenic @TimothyGu @annevk

Member

TimothyGu commented Jan 11, 2019

As tested by https://wpt.fyi/results/html/webappapis/dynamic-markup-insertion/opening-the-input-stream/history-state.window.html, that is really what UAs implement (including Firefox it seems).

Contributor Author

bzbarsky commented Jan 11, 2019

OK. Seems broken as heck to me, but....

bzbarsky closed this as completed

domenic added the topic: document.open() label

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