Issue 680785 link

Starred by 1 user

Issue metadata

Status:	WontFix
Owner:	----
Closed:	Mar 2018
Cc:	creis@chromium.org alex...@chromium.org █ nasko@chromium.org wfh@chromium.org
Components:	Internals>Sandbox>SiteIsolation UI>Browser>Navigation
EstimatedDays:	----
NextAction:	----
OS:	All
Pri:	2
Type:	Bug
Hotlist-Recharge-Cold

OOPIF: Pending remote-to-local navigation isn't canceled by a subsequent cross-site navigation

Project Member Reported by alex...@chromium.org, Jan 12 2017

Issue description

What steps will reproduce the problem?
(1) Start Chrome with --site-per-process
(2) Go to http://tests.netsekure.org/iframes/about_blank_tests.html
(3) Click "Go cross-origin" to navigate the frame cross-site.
(4) From DevTools, 
document.querySelector("iframe").src="http://tests.netsekure.org/slow.php?seconds=5"
(5) Within the next five seconds, click on "Go cross-origin" again.  

What is the expected result?
(5) should cancel the slow navigation from (4) and keep ".com" visible in the iframe.  This is what happens without --site-per-process.

What happens instead?
The navigation from (4) still succeeds, replacing the navigation that committed in (5).

The navigation in (5) doesn't have to use the same URL.  The same repro works if (5) uses 
document.querySelector("iframe").src="http://tests.netsekure.com/".  The new page shows up
and is then replaced by the page from (4) when that navigation commits.

Comment 1 Deleted

Project Member

Comment 2 by sheriffbot@chromium.org, Feb 15 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by nasko@chromium.org, Mar 29 2018

Status: WontFix (was: Untriaged)

I cannot repro with a local build as of r544068, so closing this as WontFix. I suspect changing Chrome to use PlzNavigate by default has fixed this specific issue.

►