Issue metadata
Sign in to add a comment
|
chrome://cast page blank - extensionview not displayed |
||||||||||||||||||||
Issue descriptionVersion: 54.0.2817.0 OS: OSX Steps to reproduce: (1) Go to chrome://cast (2) Observe empty page and error in JS console: VM326 extensions::guestViewContainer:212 Refused to load plugin data from '' because it violates the following Content Security Policy directive: "object-src *". (3) Go to dev tools -> Elements, right click on the extensionview element and choose "Open link in new tab". Observe the "chrome-extension://pkedcjkdefgpdelpbcmbmeomcjbeemfm/cast_setup/index.html#devices" page loading and displaying content. Expected: No error and extensionview contents displayed.
,
Aug 4 2016
paulmeyer@ has experience with this, re-assigning (Paul, re-assign it back if it turns out to be something different).
,
Aug 4 2016
I'm having trouble reproing this. I don't see the error listed in step 2, and I'm also not seeing the "open in new tab" option you describe in step 3.
,
Aug 4 2016
Are you running the latest Canary? This issue started occurring quite recently. For step 3 you have to right-click on the link shown in the 'src' attribute of the extensionview element.
,
Aug 4 2016
I was running ToT, and there was no 'src' attribute on the <extensionview> in devTools.
,
Aug 4 2016
fwiw I use the browser menu > more tools > developer tools to get the devtools for the entire page, not just the contents inside the extensionview. I was able to repro on yesterday's canary, but unable to repro on a local build that was last updated a week ago (commit 4fd767727f8a4bd4e86d626fce4921972f8180f8).
,
Aug 4 2016
You need to go to the "Elements" tab in dev tools (see screenshot). Anyway, that's just to show that the page hosted by the extension view is actually available.
,
Aug 5 2016
Confirmed as not reproducible in the latest Canary.
,
Aug 16 2016
Reopening the bug, since this is broken again in the latest canary (54.0.2830.0).
,
Aug 16 2016
,
Aug 22 2016
I'm seeing this as well.
,
Aug 30 2016
Ping. Any progress on this bug? This is a critical issue for Cast integration.
,
Aug 31 2016
This will have to be fixed before M54 goes out.
,
Aug 31 2016
After looking into this, it does not seem to be related to the bug I had encountered in the past ( Issue 539295 ). Reassigning back to wjmaclean@. On a side note, when reproing this bug, I am also seeing a second error message not mentioned by the bug reporter, which says: "Uncaught (in promise) ReferenceError: reject is not defined at ExtensionViewImpl.onLoadRejected (extensions::extensionViewApiMethods:37)". I've reported it separately ( Issue 642849 ).
,
Aug 31 2016
I meant to also mention that the second error is definitely unrelated to this bug, which is why I reported it as a separate bug.
,
Aug 31 2016
And... assigning back to myself for now.
,
Aug 31 2016
,
Aug 31 2016
This may actually be the same bug as Issue 514866.
,
Sep 6 2016
Still occurs on 54.0.2840.8
,
Sep 7 2016
Does anyone know of a build where this did work? I'm trying to find exactly when it broke.
,
Sep 7 2016
I'm hanging on to my 6/24 checkout, which is still good. However, since M53 does not have an issue, anything up to the branch point on 6/30 should still work.
,
Sep 7 2016
I think the breaking CL was commit 6104167b0bf16a3520a898dbe67227637d1c214e on June 29.
,
Sep 15 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/67b0b5d046af90992bc94390a90647d7b4a00353 commit 67b0b5d046af90992bc94390a90647d7b4a00353 Author: paulmeyer <paulmeyer@chromium.org> Date: Thu Sep 15 16:22:04 2016 Fix for chrome://cast getting blocked by content security policy. The provided policy for the cast UI was "object-src *", which used to include "chrome:" until a recent CL changed the use of “*” from a blacklist (that did not include "chrome:") to a whitelist (that still does not include "chrome:"). Because of this, the policy just needs to be updated to specifically allow "chrome:" now. BUG= 634168 Review-Url: https://codereview.chromium.org/2347503002 Cr-Commit-Position: refs/heads/master@{#418883} [modify] https://crrev.com/67b0b5d046af90992bc94390a90647d7b4a00353/chrome/browser/ui/webui/cast/cast_ui.cc
,
Sep 15 2016
,
Sep 20 2016
Requesting merge into M54: change only affects chrome://cast page. Without this change chrome://cast is completely broken.
,
Sep 20 2016
Your change meets the bar and is auto-approved for M54 (branch: 2840)
,
Sep 20 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2962c9c21ab9dd1ebd407f7dcda01c817e4f75da commit 2962c9c21ab9dd1ebd407f7dcda01c817e4f75da Author: Paul Meyer <paulmeyer@chromium.org> Date: Tue Sep 20 18:02:05 2016 Fix for chrome://cast getting blocked by content security policy. The provided policy for the cast UI was "object-src *", which used to include "chrome:" until a recent CL changed the use of “*” from a blacklist (that did not include "chrome:") to a whitelist (that still does not include "chrome:"). Because of this, the policy just needs to be updated to specifically allow "chrome:" now. BUG= 634168 Review-Url: https://codereview.chromium.org/2347503002 Cr-Commit-Position: refs/heads/master@{#418883} (cherry picked from commit 67b0b5d046af90992bc94390a90647d7b4a00353) Review URL: https://codereview.chromium.org/2350403003 . Cr-Commit-Position: refs/branch-heads/2840@{#445} Cr-Branched-From: 1ae106dbab4bddd85132d5b75c670794311f4c57-refs/heads/master@{#414607} [modify] https://crrev.com/2962c9c21ab9dd1ebd407f7dcda01c817e4f75da/chrome/browser/ui/webui/cast/cast_ui.cc
,
Sep 21 2016
Verified the issue on Mac 10.11.6 using 54.0.2840.34 and its working fine now. Please find the attached screen cast for the same.
,
Sep 26 2016
I don't see this on 55.0.2868.3
,
Oct 27 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2962c9c21ab9dd1ebd407f7dcda01c817e4f75da commit 2962c9c21ab9dd1ebd407f7dcda01c817e4f75da Author: Paul Meyer <paulmeyer@chromium.org> Date: Tue Sep 20 18:02:05 2016 Fix for chrome://cast getting blocked by content security policy. The provided policy for the cast UI was "object-src *", which used to include "chrome:" until a recent CL changed the use of “*” from a blacklist (that did not include "chrome:") to a whitelist (that still does not include "chrome:"). Because of this, the policy just needs to be updated to specifically allow "chrome:" now. BUG= 634168 Review-Url: https://codereview.chromium.org/2347503002 Cr-Commit-Position: refs/heads/master@{#418883} (cherry picked from commit 67b0b5d046af90992bc94390a90647d7b4a00353) Review URL: https://codereview.chromium.org/2350403003 . Cr-Commit-Position: refs/branch-heads/2840@{#445} Cr-Branched-From: 1ae106dbab4bddd85132d5b75c670794311f4c57-refs/heads/master@{#414607} [modify] https://crrev.com/2962c9c21ab9dd1ebd407f7dcda01c817e4f75da/chrome/browser/ui/webui/cast/cast_ui.cc |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by sheretov@chromium.org
, Aug 3 2016Owner: wjmaclean@chromium.org