Click or drag to resize

IBrowserProcessHandler Methods

Version 130.1.90

The IBrowserProcessHandler type exposes the following members.

Methods
 NameDescription
Public methodDisposePerforms application-defined tasks associated with freeing, releasing, or resetting unmanaged resources.
(Inherited from IDisposable)
Public methodOnAlreadyRunningAppRelaunch Implement this method to provide app-specific behavior when an already running app is relaunched with the same CefSettings.RootCachePath value. For example, activate an existing app window or create a new app window. To avoid cache corruption only a single app instance is allowed to run for a given CefSettings.RootCachePath value. On relaunch the app checks a process singleton lock and then forwards the new launch arguments to the already running app process before exiting early. Client apps should therefore check the Cef.Initialize() return value for early exit before proceeding. It's important to note that this method will be called on a CEF UI thread, which by default is not the same as your application UI thread.
Public methodOnContextInitialized Called on the CEF UI thread immediately after the CEF context has been initialized. You can now access the Global RequestContext through Cef.GetGlobalRequestContext() - this is the first place you can set Preferences (e.g. proxy settings, spell check dictionaries).
Public methodOnScheduleMessagePumpWork Called from any thread when work has been scheduled for the browser process main (UI) thread. This callback is used in combination with CefSettings. ExternalMessagePump and Cef.DoMessageLoopWork() in cases where the CEF message loop must be integrated into an existing application message loop (see additional comments and warnings on Cef.DoMessageLoopWork). This callback should schedule a Cef.DoMessageLoopWork() call to happen on the main (UI) thread.
Top
See Also