Issue metadata
Sign in to add a comment
|
Flag --unsafely-treat-insecure-origin-as-secure not working with requestMediaKeySystemAccess
Reported by
tho...@couchfunk.de,
Dec 13 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 Steps to reproduce the problem: 1. Open chrome with `google-chrome --unsafely-treat-insecure-origin-as-secure="http://example.com" --user-data-dir=~/temp/chrome/Profile` 2. Chrome will open with a message about an unsupported flag. 3. Open `http://example.com` 4. Open the Developer Console 5. Type `navigator.requestMediaKeysystemAccess` 6. The console will output `undefined` Steps to verify that `requestMediaKeysystemAccess` is in fact available: 1. Open `https://google.com` 2. Open the Developer Console 3. Type `navigator.requestMediaKeysystemAccess` 4. The console will output `function ...` What is the expected behavior? The requestMediaKeysystemAccess funciton should exist on all insecure origins set inside the flag. After step 4 the console should output `function...`. What went wrong? The browser does not enable HTTPS only features despite setting the flag --unsafely-treat-insecure-origin-as-secure Did this work before? No Does this work in other browsers? Yes Chrome version: 63.0.3239.84 Channel: stable OS Version: Ubuntu 17.04 Flash Version:
,
Dec 13 2017
This is no longer working with service workers either - Windows 10 Home 64 bit.
,
Dec 13 2017
,
Dec 13 2017
Dupe of crbug.com/792993 . I'd mark it as dupe; except I'm not at work and don't have my chromium.org account set up here. :-/ - The reporter is correct, as are the observations in #1 + #2. - The flag is broken in M63. It works fine in M64 & subsequent versions. - The release owners have decided to not do a re-release of M63. See 792993. - The official workaround is - since this is mainly a developer/debug feature - to use the M64 beta version for the time being. - Meanwhile, an end-to-end test for the flag has been added to ensure this will not happen again. I'm sorry for the inconvenience.
,
Dec 14 2017
Thanks for the clarification. I'm sorry for the dupe. Is the beta version not available for debianish linux, yet? google-chrome-beta is still version 63.
,
Dec 14 2017
#5: - Chrome Linux M64 beta indeed isn't out just yet. Should be any day now. - Thanks for the report. Duplicate reports are fine; in fact, they give us additional info about the severity of the problem. It's just important that we merge them all into the 'main' bug. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by tho...@couchfunk.de
, Dec 13 2017