Change to using Chrome bootstrap by default

[amaitland]

CEF is removing the Alloy Bootstrap (#4795) in M128.

In M126 we will switch to using the Chrome Bootstrap by default.

For a limited time you will be able to revert to using the Alloy bootstrap by setting CefSettings.ChromeRuntime to false.

cefSettings.ChromeRuntime = false;

---

Important

If you discover an issue with the Chrome Bootstrap then you need to raise the issue on the CEF ISSUE TRACKER

https://github.com/chromiumembedded/cef/issues

Please post a link in #4795 for reference, don't create an issue in this repository.

---

chromiumembedded/cef#3685

[amaitland]

CefSharpSettings.RuntimeStyle has been added to simplify switching to using the Chrome styled windows. This is a global setting, must be set before creating your first ChromiumWebBrowser instance.

CefSharpSettings.RuntimeStyle = CefRuntimeStyle.Chrome;

Behaviour can be controller on a per ChromiumWebBrowser instance via overriding ChromiumWebBrowser.CreateBrowserWindowInfo.

This is only for WinForms and Wpf.HwndHost. The OffScreen and WPF implementations will always use Alloy styled windows (that's all CEF supports, the property is ignored for offscreen rendering).

[amaitland]

For a limited time you will be able to revert to using the Alloy bootstrap by setting CefSettings.ChromeRuntime to false.

cefSettings.ChromeRuntime = false;

Once chromiumembedded/cef#3685 has been resolved the Alloy bootstrap will be removed.

CEF has it's own support forum and issue tracker should you discover any bugs or changes in behaviour with the Chrome bootstrap, you can discuss them on the forum or raise issues on the issue tracker.

• https://www.magpcss.org/ceforum/index.php
• https://github.com/chromiumembedded/cef/issues

[amaitland]

CefSharpSettings.RuntimeStyle has been added to simplify switching to using the Chrome styled windows. This is a global setting, must be set before creating your first ChromiumWebBrowser instance.

For those using the Chrome runtime currently will need to change the runtime style to Chrome to keep the same behaviour.

[amaitland]

Known issues

• v126.x (Chrome bootstrap) unable to load cookies from prior version (Alloy bootstrap) #4847

[amaitland]

Important

If you discover an issue with the Chrome Bootstrap then you need to raise the issue on the CEF ISSUE TRACKER

https://github.com/chromiumembedded/cef/issues

Please post a link here for reference, don't create an issue in this repository.

[amaitland]

If you discover an issue with the Chrome Bootstrap then you need to raise the issue on the CEF ISSUE TRACKER

https://github.com/chromiumembedded/cef/issues

If something doesn't work with the Chrome bootstrap and you switch back to the Alloy bootstrap and it works as expected then you'll need to raise an issue on https://github.com/chromiumembedded/cef/issues

In the short term keep using the Alloy bootstrap until the bug is fixed upstream

[amaitland]

The Alloy bootstrap will be removed upstream in M128

[amaitland]

The disable-pdf-extension flag is not supported with Chrome bootstrap.

[amaitland]

Known issues

List at #4795

[chacham2]

The disable-pdf-extension flag is not supported with Chrome bootstrap.

Will it ever be?

[max3163]

Add link to chromiumembedded/cef#3785

[amaitland]

List of known issues is now at #4795 (comment)

Links have been updated, going forward will just keep the list updated there (if you find an upstream issue that effects CefSharp then please add the link in #4795)