New issue
Advanced search Search tips

Issue 713364 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 1
Type: Bug

Blocking:
issue 623682
issue 711443



Sign in to add a comment

Feature policy is not initialized correctly in browser for frames which have not navigated

Project Member Reported by iclell...@chromium.org, Apr 19 2017

Issue description

An error in the DidNavigate code for FeaturePolicy means that frames which are inserted into a document with their src url already set never trigger the condition which resets the feature policy in the RenderFrameHostImpl.
 

Comment 1 by creis@chromium.org, Apr 19 2017

Cc: creis@chromium.org
Components: UI>Browser>Navigation
Blocking: 623682 711443
This appears to be happening because inserting a frame into a document loads the frame's URL with transition type PAGE_TRANSITION_AUTO_SUBFRAME, which causes |did_navigate| in NavigatorImpl::DidNavigate() to be false, and so RFHI::ResetFeaturePolicy does not get called.
Status: Fixed (was: Started)

Sign in to add a comment