-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move CefSettings into Wpf, WinForms and Offscreen namespaces #2477
Comments
Additionally |
Resolved in d87e795 |
…ersion - This is a breaking change as there is no common `CefSharp.CefSettings`, there is no `CefSharp.Wpf.CefSettings`, `CefSharp.WinForms.CefSettings` and `CefSharp.OffScreen.CefSettings` - Cef.Initialize has been removed, the `ChromiumWebBrowser` constructor will call the `Cef.Initialize` with the defaults for your flavour - CefSettings.FocusedNodeChangedEnabled has been moved to CefSharpSettings.FocusedNodeChangedEnabled Resolves #2477
|
CefSharp.CefSettings is now CefSharp.WinForms.CefSettings/CefSharp.Wpf.CefSettings/CefSharp.OffScreen.CefSettings See cefsharp/CefSharp#2477 for more details There is one set of settings for each flavour, all the essential command line workarounds are enabled (there are plenty of non-essential ones that have no yet been enabled by default)
As part of these changes Example Cef.Initialize(); //THIS LINE NEEDS TO BE REMOVED AND IS SAFE TO DO SO
browser = new ChromiumWebBrowser() |
To allow for custom settings/command line arguments to be set for the different flavours, this has become more and more important for the
WPF/OffScreens
versions.This will be a minor breaking change, you may need to add an additional using statement as
CefSettings
will no longer be in theCefSharp
namespace, there will be a specific version forWPF
,WinForms
andOffScreen
.For
WinForms
addusing CefSharp.WinForms;
For
Wpf
addusing CefSharp.Wpf;
For
OffScreen
addusing CefSharp.OffScreen;
The
Cef.Initialize()
method will be removed, it's not required, the first instance ofChromiumWebBrowser
you create willInitialize
with the default settings if you haven't really calledCef.Initialize
yourself.The text was updated successfully, but these errors were encountered: