New issue
Advanced search Search tips

Issue 623681 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug
Proj-Servicification

Blocking:
issue 236848



Sign in to add a comment

OOPIF: In-page navigations do not preserve subframe FrameNavigationEntries

Project Member Reported by creis@chromium.org, Jun 27 2016

Issue description

Version: 53.0.2780.0
OS: All

What steps will reproduce the problem?
(0) Start Chrome with --isolate-extensions.
(1) Visit http://csreis.github.io/tests/cross-site-iframe.html
(2) Click Go same-site
(3) Add "#foo" to the URL and hit enter.
(4) Visit http://csreis.github.io/tests/
(5) Go back.

What is the expected output?

The iframe should be on "Simple page."

What do you see instead?

The iframe is on "Initial page."

This also causes some layout tests to fail:
Repro steps:
  $ DISPLAY=:20 third_party/WebKit/Tools/Scripts/run-webkit-tests \
      -t Release -v --additional-drt-flag=--isolate-sites-for-testing=*.is \
      --no-retry-failures --additional-drt-flag=--no-sandbox \
      fast/history/same-document-iframes-changing-fragment.html \
      fast/history/same-document-iframes-changing-pushstate.html

The problem is that NavigationControllerImpl::RendererDidNavigateToNewPage doesn't put any subframe FrameNavigationEntries in the new NavigationEntry after an in-page navigation.

This happens with SiteIsolationPolicy::UseSubframeNavigationEntries(), whether any OOPIFs are present or not.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Jul 26 2016

Comment 2 by creis@chromium.org, Jul 26 2016

Status: Fixed (was: Assigned)

Comment 3 by laforge@google.com, Nov 7 2017

Components: Internals>Network>Service

Comment 4 by laforge@google.com, Nov 7 2017

Components: -Internals>Network>Service Internals>Services>Network
Apologies, applied the wrong component in bulk.

Sign in to add a comment