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

Issue 872908 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome Apps CSP blocking Google Cast support in Chrome Beta 69

Reported by gra...@kennery.com, Aug 9

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1. Attempt to create a script element within a Chrome app to load the cast framework `chrome-extension://pkedcjkdefgpdelpbcmbmeomcjbeemfm/cast_sender.js`
2. Open network tab
3. Observe that the script is blocked

What is the expected behavior?
That Cast API will be available

What went wrong?
The Cast API is being blocked from loading.

Did this work before? Yes Version 68.0.3440.106 (Official Build) (64-bit)

Does this work in other browsers? N/A

Chrome version: 69.0.3497.32  Channel: beta
OS Version: OS X 10.13.6
Flash Version: 

We've been using the cast SDK within a Chrome App for years - and we've always done it by finding the appropriate cast extension ID and loading the `cast_sender.js` into our Chrome App.

The most recent Chrome Beta is blocking the script from loading because of the Chrome App CSP all of a sudden.
 
Labels: Needs-Bisect Needs-Triage-M69
Cc: phanindra.mandapaka@chromium.org
Labels: Triaged-ET Needs-Feedback
Thanks for filling the issue...

@Reporter :Tried with given URL  as we are Unable to create a script element, It would be really helpful if a sample URL is provided, so that we can investigate the issue further.

Thanks.!
Components: -Blink>SecurityFeature Blink>SecurityFeature>ContentSecurityPolicy
Owner: andypaicu@chromium.org
Status: Assigned (was: Unconfirmed)
Hi! It would be helpful if you could provide an error message from the console. Generally speaking, we ought to be allowing `chrome-extension://` resources to be embedded in pages.

Sign in to add a comment