This influences the behavior of RegisterAsyncJsObject and how method calls are made. By default the [!:MethodRunnerQueue] executes Tasks in a sync fashion. Setting this property to true will allocate new Tasks on TaskScheduler.Default for execution.

Objects registered using RegisterJsObject and RegisterAsyncJsObject will be automatically bound in the first render process that's created for a ChromiumWebBrowser instance. If you perform a cross-site navigation a process switch will occur and bound objects will no longer be automatically avaliable. For those upgrading from version 57 or below that do no perform cross-site navigation (e.g. Single Page applications or applications that only refer to a single domain) can set this property to true and use the old behaviour.Defaults to false NOTE: Set this before your first call to RegisterJsObject or RegisterAsyncJsObject

The proxy options that will be used for all connections If set before the call to Cef.Initialize, command line arguments will be set for you If a username and password is provided and the IPs match authentication is done automatically NOTE: GetAuthCredentials won't be called for a proxy server that matches the IP NOTE: It isn't possble to change the proxy after the call to Cef.Initialize

For the WinForms and WPF instances of ChromiumWebBrowser the relevant Application Exit event is hooked and Cef.Shutdown() called by default. Set this to false to disable this behaviour. This value needs to be set before the first instance of ChromiumWebBrowser is created as the event handlers are hooked in the static constructor for the ChromiumWebBrowser class

WCF is used by RegisterJsObject feature for Javascript Binding It's reccomended that anyone developing a new application use the RegisterAsyncJsObject version which communicates using native Chromium IPC.

Change the Close timeout for the WCF channel used by the sync JSB binding. The default value is currently 2 seconds. Changing this to Zero will result on Abort() being called on the WCF Channel Host