Enable Chromium Site Isolation

[amaitland]

CEF recently added support for https://bitbucket.org/chromiumembedded/cef/issues/2498/add-support-for-site-per-process

We should now look at properly supporting the process model as it's now the CEF default.

• Remove process-per-site-instance command line arg from CefSettings

Related issue #2553

[amaitland]

WPF version will require disable-site-isolation-trials command line arg until upstream issue #2789 has been resolved

[amaitland]

https://bitbucket.org/chromiumembedded/cef/issues/2814/process-messages-cant-be-sent-to-all

[amaitland]

Site isolation trials disabled for all WPF/WinForms/OffScreen in commit 93336a0 Now using the default process model (chromium site isolation project)

[amaitland]

WPF version will require disable-site-isolation-trials command line arg until upstream issue #2789 has been resolved

This has been resolved (builds haven't been updated yet)

https://bitbucket.org/chromiumembedded/cef/issues/2814/process-messages-cant-be-sent-to-all

Cannot remove disable-site-isolation-trials until this is solved.

[amaitland]

Issue is now tracked at https://bitbucket.org/chromiumembedded/cef/issues/2849/siteisolation-process-message-from-browser

[amaitland]

Issue has been resolved see https://bitbucket.org/chromiumembedded/cef/issues/2849/siteisolation-process-message-from-browser#comment-60550396

There are potential changes to how frames are handled that need to be evaluated.

[amaitland]

This means that frame objects (including for the main frame) will now always change after cross-origin navigation, and the old frame object will be invalidated.

Cross origin navigations now invalidate the main frame.

[amaitland]

With site isolation enabled many of the tests (pretty much anything that uses the IPC) will fail, so reverting for now and reopening.

[amaitland]

Adding this to the 94 milestone as a reminder to revisit, debugging should be done before Chrome decides to remove disable-site-isolation-trials and we're forced to upgrade.

[StefanoBalzarottiEnnova]

When do you plan to fix this issue? There is a workaround to use CEFSharp with site isolation? This feature is critical for my application,

[NinjaCross]

This is highly critical fro my company too.
Is there a release date for this ?

[amaitland]

There is nothing stopping you from using site isolation now, it's simply disabled by default. You can remove the disable-site-isolation-trials command line arg and test your application.

This isn't really something that I can fix directly, it'll be reporting any problems upstream and waiting for a fix.

[amaitland]

Commit 221185b enabled site isolation by default for master

The CanLoadRequestWithPostData test has been updated in commit fd78c0c to native to a domain of the same origin before attempting to call LoadRequest.

LoadRequest calls will fail otherwise as discussed at https://magpcss.org/ceforum/viewtopic.php?f=10&t=18672&p=50266#p50249

Tests are passing with the exception of IntegrationTestFacts.LoadLegacyJavaScriptBindingQunitTestsSuccessfulCompletion. Same test passes when I run it through Visual Studio Test Explorer. A new issue should be created and debugged at some point to determine the cause and evaluate if it's fixable or if upstream changes are required.

At this point I'll leave Site Isolation enabled by default for version 95 which can be disabled if required.

[amaitland]

Chromium Site Isolation is now enabled by default in 95.7.140-pre which is now available for testing.

You can still manually disable via the disable-site-isolation-trials command line arg. e.g.

var settings = new CefSettings()
{
	//By default CefSharp will use an in-memory cache, you need to specify a Cache Folder to persist data
	CachePath = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData), "CefSharp\\Cache")
};

settings.CefCommandLineArgs.Add("disable-site-isolation-trials");

Cef.Initialize(settings, performDependencyCheck: true, browserProcessHandler: null);

Tests are passing with the exception of IntegrationTestFacts.LoadLegacyJavaScriptBindingQunitTestsSuccessfulCompletion. Same test passes when I run it through Visual Studio Test Explorer. A new issue should be created and debugged at some point to determine the cause and evaluate if it's fixable or if upstream changes are required.

Issue #3867 has been created to track investigating the failures. Any problems using Legacy JavaScript Binding then you'll need to disable Chromium Site Isolation

---

If you are using CefSharp in a commercial product and not already a sponsor then please consider supporting my efforts. Developing/maintaining/supporting the project takes a considerable amount of time.

[amaitland]

Known behaviour changes in CEF are as follows: - A spare renderer process may be created on initial browser creation or cross- origin navigation. This spare process may be used with a future cross-origin navigation or discarded on application shutdown.

As per chromiumembedded/cef#2498 (comment).

With Site Isolation enabled it's expected there is a spare render process is created and will exist until Cef.Shutdown has been called.