chrome-extension:// throws a mixed-content error when remote debugging
Reported by
the.sp...@gmail.com,
Sep 1 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: 1. Install the extension from folder 2. Open google.com on Android Chrome 3. Open DevTools on that target 4. Go to PerfMeter tab, hit Reload What is the expected behavior? A div called perfmeter-panel should be created on the top right corner, with background-color rgba( 0, 0, 0, .5 ) and some more CSS styles from styles.css What went wrong? When remote debugging, it doesn't load styles.css, throwing the error: Mixed Content: The page at 'https://www.google.es/?gfe_rd=cr&ei=PX3IV_fvAoqt8we_gaPwBw&gws_rd=ssl' was loaded over HTTPS, but requested an insecure stylesheet 'chrome-extension://ecnchfeibidccgndhhiejeaajjdiimgm/css/styles.css'. This request has been blocked; the content must be served over HTTPS. WebStore page: https://github.com/spite/PerfMeter Did this work before? No Chrome version: 52.0.2743.116 Channel: stable OS Version: OS X 10.11.6 Flash Version: It does work when debugging normally with DevTools.
,
Sep 2 2016
,
Dec 20 2016
Jaume and I just talked about this during our bi-weekly sync-ups and he's still running into it. Since it's affecting his and other developers' work on Android I'm marking this ReleaseBlock-Stable and targeting it at M57.
,
Jan 5 2017
Gentle Ping !! @caseq -- Any update on this issue.
,
Jan 17 2017
Gentle Ping !! As it is marked as ReleaseBlock- Stable , Could we get any update on this issue. Thanks!
,
Feb 2 2017
kbr@/caseq@: Could you please update the issue if there is any progress on it.
,
Feb 5 2017
It's still an issue. Andrey, could you please triage this bug? It's impacting an advanced extension developer's work. Thanks.
,
Feb 8 2017
So what happens here is that you're apparently trying to inject a resource from your extension into the page being debugged remotely, over the protocol. The extension is not necessarily available on the target page (any in case of mobile, the extensions are just not supported). I guess the best way to workaround that would be to inject an inline <style> element (e.g. with the help of eval()). Please ping me directly if you need more help with that. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by paulir...@chromium.org
, Sep 2 2016Status: Assigned (was: Unconfirmed)