New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 705550 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Global history stack is breaks when an iframe is removed

Project Member Reported by dvoytenko@google.com, Mar 27 2017

Issue description

Chrome 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.

 

Comment 1 by ojan@chromium.org, Mar 29 2017

Cc: slangley@chromium.org sashab@chromium.org dcheng@chromium.org nasko@chromium.org ojan@chromium.org
Components: Blink>Internals>Frames
I agree this seems like a bug. I'm not quite sure which team owns history at this point, but I think it's probably one of the folks I'm CCing here. :)

Comment 2 by dcheng@chromium.org, Mar 29 2017

Components: -Blink>Internals>Frames UI>Browser>History
Owner: creis@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by dcheng@chromium.org, Mar 29 2017

Cc: japhet@chromium.org

Comment 4 by dcheng@chromium.org, Mar 29 2017

Components: -UI>Browser>History UI>Browser>Navigation

Comment 5 by dcheng@chromium.org, Mar 29 2017

This doesn't seem to reproduce reliably for me, FWIW. Maybe I'm doing something wrong?
Reproduces 100% with the instructions above. But sometimes it's hard to spot the refresh - it's very fast.

Comment 7 by ojan@chromium.org, Mar 29 2017

Looking at the console getting cleared is the easiest way to see that it refreshed.
Project Member

Comment 8 by sheriffbot@chromium.org, Jul 21 2017

Labels: Hotlist-Google
Cc: -sashab@chromium.org

Comment 10 by ojan@chromium.org, May 8 2018

Cc: -ojan@chromium.org

Sign in to add a comment