From e99df52a746b4f567093cc2871f115b9c983f694 Mon Sep 17 00:00:00 2001
From: gkostov <p_e_a@gbg.bg>
Date: Sun, 14 Jul 2019 17:22:10 +0300
Subject: [PATCH] added "--disable-site-isolation-trials" to
 Chrome_without_security

This SO page https://stackoverflow.com/questions/53080472/chrome-disable-web-security-no-longer-works got me to what has been described here https://www.chromium.org/Home/chromium-security/site-isolation#TOC-Known-Issues so I thought it will be useful for others if the docs mention that fact :)

macOS 10.14, Chrome 75.0.3770.100
I had a problem testing a site and kept getting "Error: Uncaught SecurityError: Blocked a frame with origin..." even if I had provided "--disable-web-security" as per the example in the documentation. Seems Chrome has changed its security policies and that flag is no longer enough to get it out of the the CORS cage.
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 34dd169..fb72e95 100644
--- a/README.md
+++ b/README.md
@@ -28,7 +28,7 @@ module.exports = function(config) {
     customLaunchers: {
       Chrome_without_security: {
         base: 'Chrome',
-        flags: ['--disable-web-security']
+        flags: ['--disable-web-security', '--disable-site-isolation-trials']
       }
     }
   })