-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Which location should reload on history.go(0)? #2436
Comments
cc @annevk |
IRC chat on #servo with @KiChjang and @bzbarsky: http://logs.glob.uno/?c=mozilla%23servo&s=14+Mar+2017&e=14+Mar+2017#c630800 "The problem is that if you call childWindow.go(0), what if you are same-origin with the child, but x-origin with the parent?" |
This basically depends on #1454 being fixed I think. |
Well it's related to #1454, but orthogonal. Currently the spec special-cases |
But making history more of a flat concept should help a lot with deciding what to reload I think. |
This is also related to #2018 (should history return cross-origin information). |
See whatwg/html#2436. Specified in whatwg/html#6315.
See whatwg/html#2436. Specified in whatwg/html#6315.
See whatwg/html#2436. Specified in whatwg/html#6315.
See whatwg/html#2436. Specified in whatwg/html#6315.
See whatwg/html#2436. Specified in whatwg/html#6315.
…s, a=testonly Automatic update from web-platform-tests Test which document history.go(0) reloads See whatwg/html#2436. Specified in whatwg/html#6315. -- wpt-commits: df228765793c58a9a7aa25c8b808df529e049122 wpt-pr: 36366
…s, a=testonly Automatic update from web-platform-tests Test which document history.go(0) reloads See whatwg/html#2436. Specified in whatwg/html#6315. -- wpt-commits: df228765793c58a9a7aa25c8b808df529e049122 wpt-pr: 36366
The spec for
history.go()
at https://html.spec.whatwg.org/multipage/browsers.html#dom-history-go says:This is ambiguous as to which
location
should be used, the one for the window whose history is being accessed, or the current document. Unfortunately, different browsers behave differently, as shown by:Under FF, this will loop forever reloading (because the main document is reloaded) whereas in Chrome it will terminate (because the child is reloaded).
The text was updated successfully, but these errors were encountered: