Global history stack is breaks when an iframe is removed |
|||||||
Issue descriptionChrome Version: (copy from chrome://version) OS: (e.g. Win7, OSX 10.9.5, etc...) macOSX 10.12.2 (16C67) Chrome: 59.0.3048.0 canary (64-bit) What steps will reproduce the problem? (1) Open http://output.jsbin.com/zuhoqiz/quiet (2) Click "Push State" couple of times in the PARENT doc. This will call pushState on top window's history object. (3) Click "Push State" couple of times INSIDE the iframe. This will call pushState on iframe's local history object. (4) Click on "Kill iframe" in the parent doc. This will remove iframe from DOM. (5) Click "Back" button - browser or in parent doc, doesn't matter. Observe: The parent page is reloaded. You can see this in the console and also by the fact that iframe is on the page again. What is the expected result? Expected the parent window context to be tolerant and continue to function. Possibly purge the history entries created by the removed iframe. This appears how Firefox is handling this situation.
,
Mar 29 2017
,
Mar 29 2017
,
Mar 29 2017
,
Mar 29 2017
This doesn't seem to reproduce reliably for me, FWIW. Maybe I'm doing something wrong?
,
Mar 29 2017
Reproduces 100% with the instructions above. But sometimes it's hard to spot the refresh - it's very fast.
,
Mar 29 2017
Looking at the console getting cleared is the easiest way to see that it refreshed.
,
Jul 21 2017
,
Feb 2 2018
,
May 8 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ojan@chromium.org
, Mar 29 2017Components: Blink>Internals>Frames