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

Issue 840533 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

ManifestManager runs on all Frames accidentally?

Project Member Reported by ajwong@chromium.org, May 7 2018

Issue description

Reading through RenderFrameImpl's initialization, I noticed this code:

https://chromium-review.googlesource.com/c/chromium/src/+/774040/6/content/renderer/render_frame_impl.cc#1360

which looks like it always executes even child frames. The reason is IsMainFrame() doesn't return a value signal until it is set in RenderFrameImpl::Initialize().  Thus the conditional in the constructor always returns true.

What is ManifestManager and would it be bad to just move it into the ::Initialize() method?
 
Cc: nasko@chromium.org dcheng@chromium.org

Comment 2 by dcheng@chromium.org, May 21 2018

Cc: dominickn@chromium.org mlamouri@chromium.org
Components: Blink>AppManifest
Labels: -Pri-3 Pri-2
Status: Assigned (was: Untriaged)
This is the implementation of the web app manifest (https://www.w3.org/TR/appmanifest/) in Chrome. The ManifestChangeNotifier will run a callback if the site changes its <link rel="manifest"> tag to point to a new file.

It's probably fine to move the construction of the ManifestChangeNotifier from the RenderFrameImpl constructor to Initialize().

Sign in to add a comment