Disclosure Statement: This site contains affiliate links, which means that I may receive a commission if you make a purchase using these links. As an eBay Partner, I earn from qualifying purchases.
Update to CEF 3.3239.1723.g071d1c1
Re: Update to CEF 3.3239.1723.g071d1c1
Hello! Salvador so whats the news? Seems like not only me having problems with newer versions. I couldnt initialize and run even demo app in one of the previous topics on Delphi 2010 if you remember. Any update on this?
- salvadordf
- Posts: 4564
- Joined: Thu Feb 02, 2017 12:24 pm
- Location: Spain
- Contact:
Re: Update to CEF 3.3239.1723.g071d1c1
Hi,
I replied your message a few days ago. Sorry for the delay but I was very busy.
https://www.briskbard.com/forum/viewtop ... p=902#p911
I replied your message a few days ago. Sorry for the delay but I was very busy.
https://www.briskbard.com/forum/viewtop ... p=902#p911
Re: Update to CEF 3.3239.1723.g071d1c1
SitePerProcess:= False;salvadordf wrote: Sun Jan 14, 2018 5:45 pm I'm afraid I don't know if Google changed the cross-origin policy in Chromium.
Perhaps this is a consequence of having GlobalCEFAp.SitePerProcess set to True by default.
Try setting GlobalCEFAp.SitePerProcess to False or adding GlobalCEFAp.AddCustomCommandLine('--disable-websecurity') before the GlobalCEFAp.StartMainProcess call in the DPR file.
х86 Nice!
x64 does not work.
x64 wrote:Uncaught SecurityError: Blocked a frame with origin "http://www.****.net" from accessing a frame with origin "https://www.google.com". The frame requesting access has a protocol of "http", the frame being accessed has a protocol of "https". Protocols must match.
- salvadordf
- Posts: 4564
- Joined: Thu Feb 02, 2017 12:24 pm
- Location: Spain
- Contact:
Re: Update to CEF 3.3239.1723.g071d1c1
I'm beginning to think Google announced this feature too early and I enabled it too soon.
This is called "Strict site isolation" in Chromium. It's considered "Highly experimental" an it's disabled by default in that browser.

This is called "Strict site isolation" in Chromium. It's considered "Highly experimental" an it's disabled by default in that browser.
Re: Update to CEF 3.3239.1723.g071d1c1
But why it works in x86, but on x64 no?
- salvadordf
- Posts: 4564
- Joined: Thu Feb 02, 2017 12:24 pm
- Location: Spain
- Contact:
Re: Update to CEF 3.3239.1723.g071d1c1
I don't know. It's a chromium bug.
Re: Update to CEF 3.3239.1723.g071d1c1

Not correct
GlobalCEFApp.AddCustomCommandLine('--disable-websecurity');
Correctly
GlobalCEFApp.AddCustomCommandLine('--disable-web-security');
And everything works!
It would be necessary to include it in the setup
Chromium1.Options.WebSecurity := STATE_DISABLED;
- salvadordf
- Posts: 4564
- Joined: Thu Feb 02, 2017 12:24 pm
- Location: Spain
- Contact:
Re: Update to CEF 3.3239.1723.g071d1c1
Sorry for the typo
You can also set GlobalCEFApp.DisableWebSecurity to True to add the same command line switch.

You can also set GlobalCEFApp.DisableWebSecurity to True to add the same command line switch.
Re: Update to CEF 3.3239.1723.g071d1c1
Clearly

But why is this setting not working?
Chromium1.Options.WebSecurity := STATE_DISABLED;
- salvadordf
- Posts: 4564
- Joined: Thu Feb 02, 2017 12:24 pm
- Location: Spain
- Contact:
Re: Update to CEF 3.3239.1723.g071d1c1
Chromium1.Options.WebSecurity is passed to the TCefBrowserSettings to create the browser.
It seems that blink is ignoring that setting (a bug in chromium?)
It seems that blink is ignoring that setting (a bug in chromium?)