No way to allow externally_connectable from about:blank
Reported by
brkic.go...@mainframe2.com,
May 16 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Append empty iframe to document 2. Write content in it (using template engine) 3. Try to connect with wrapper Chrome Application What is the expected behavior? Web page is able to connect What went wrong? Connection is blocked without error message. Did this work before? No Does this work in other browsers? N/A Chrome version: 58.0.3029.110 Channel: stable OS Version: OS X 10.12.4 Flash Version: Use case is simple: We have a player which, if detects that it is run inside of a Chrome application, enables additional features. There is no need for contents of this IFrame to be retrieved from the website, when we can pack it inside of a local bundle.
,
May 16 2017
@brkic.goran-- Could you please provide us the testurl/sample test file to reproduce the issue , that would help us in traiging the issue better. Thanks!
,
Jun 2 2017
@brkic.goran - please provide a sample html file that demonstrates the problem.
,
Jun 6 2017
[mac bug triage] I'm assuming that "externally_connectable" here is referring to the Chrome extension manifest property (docs here: https://developer.chrome.com/extensions/manifest/externally_connectable). Tentatively tagging Platform>Extensions>API.
,
Jan 22 2018
Mac bug triage: WontFix old bug with no repro steps. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ranjitkan@chromium.org
, May 16 2017