Issue metadata
Sign in to add a comment
|
Feature request: Flag that does the opposite of IsolationOrigins
Reported by
shane.af...@gmail.com,
Mar 6 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Steps to reproduce the problem: https://www.chromium.org/administrators/policy-list-3#IsolateOrigins IsolateOrigins allows you to specify named origins in a comma-separated list that will run in its own process. I'm wondering if it would be possible to implement a flag that does the opposite: enable strict site isolation for everything _except_ "domain.xyz". What is the expected behavior? What went wrong? Feature request: This will allow Enterprise policies to isolate everything except for a known set of internal URLs, to temporarily work around any issues in usability. Did this work before? N/A Chrome version: 64.0.3282.186 Channel: stable OS Version: OS X 10.12.6 Flash Version:
,
Mar 6 2018
Thanks for the report. There's some discussion of this in issue 806905 , so I'll mark this as a duplicate. Specifically, see https://bugs.chromium.org/p/chromium/issues/detail?id=806905#c5 for why this isn't as straightforward as it seems. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by csharrison@chromium.org
, Mar 6 2018