All Classes, Interfaces, Objects and Records

Custom interface used to handle all the TCefApplicationCore events.

Implement this interface to provide handler implementations. Methods will be called by the process and/or thread indicated.

Callback interface used for asynchronous continuation of authentication requests.

Callback interface used to asynchronously continue a download.

A Layout manager that arranges child views vertically or horizontally in a side-by-side fashion with spacing around and between the child views. The child views are always sized according to their preferred size. If the host's bounds provide insufficient space, child views will be clamped. Excess space will not be distributed. Methods must be called on the browser process UI thread unless otherwise indicated.

Interface used to represent the browser process aspects of a browser. The functions of this interface can only be called in the browser process. They may be called on any thread in that process unless otherwise indicated in the comments.

A View hosting a ICefBrowser instance. Methods must be called on the browser process UI thread unless otherwise indicated.

Custom interface used to handle all the ICefBrowserViewDelegate events.

Implement this interface to handle Button events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.

Generic callback interface used for asynchronous continuation.

Implement this interface to handle events related to commands. The functions of this interface will be called on the UI thread.

Generic callback interface used for asynchronous completion.

Provides information about the context menu state. The functions of this interface can only be accessed on browser process the UI thread.

Interface used for managing cookies. The functions of this interface may be called on any thread unless otherwise indicated.

Interface used to read data from a stream. The functions of this interface may be called on any thread.

Callback interface for ICefBrowserHost.AddDevToolsMessageObserver. The functions of this interface will be called on the browser process UI thread.

Interface representing a dictionary value. Can be used on any process and thread.

Implement this interface to handle events related to browser display state. The functions of this interface will be called on the UI thread.

Interface used to represent a DOM node. The functions of this interface should only be called on the render process main thread.

Interface used to handle file downloads. The functions of this interface will called on the browser process UI thread.

Interface used to represent a download item.

Interface used to represent drag data. The functions of this interface may be called on any thread.

Implement this interface to receive notification when tracing has completed. The functions of this interface will be called on the browser process UI thread.

Implement this interface to handle events related to browser extensions. The functions of this interface will be called on the UI thread. See ICefRequestContext.LoadExtension for information about extension loading.

A simple Layout that causes the associated Panel's one child to be sized to match the bounds of its parent. Methods must be called on the browser process UI thread unless otherwise indicated.

Implement this interface to handle events related to focus. The functions of this interface will be called on the UI thread.

Implement this interface to handle events related to ICefFrame life span. The order of callbacks is:

(1) During initial ICefBrowserHost creation and navigation of the main frame: - ICefFrameHandler.OnFrameCreated => The initial main frame object has been created. Any commands will be queued until the frame is attached. - ICefFrameHandler.OnMainFrameChanged => The initial main frame object has been assigned to the browser. - ICefLifeSpanHandler.OnAfterCreated => The browser is now valid and can be used. - ICefFrameHandler.OnFrameAttached => The initial main frame object is now connected to its peer in the renderer process. Commands can be routed.

(2) During further ICefBrowserHost navigation/loading of the main frame and/or sub-frames: - ICefFrameHandler.OnFrameCreated => A new main frame or sub-frame object has been created. Any commands will be queued until the frame is attached. - ICefFrameHandler.OnFrameAttached => A new main frame or sub-frame object is now connected to its peer in the renderer process. Commands can be routed. - ICefFrameHandler.OnFrameDetached => An existing main frame or sub- frame object has lost its connection to the renderer process. If multiple objects are detached at the same time then notifications will be sent for any sub-frame objects before the main frame object. Commands can no longer be routed and will be discarded. - ICefFrameHandler.OnMainFrameChanged => A new main frame object has been assigned to the browser. This will only occur with cross-origin navigation or re-navigation after renderer process termination (due to crashes, etc).

(3) During final ICefBrowserHost destruction of the main frame: - ICefFrameHandler.OnFrameDetached => Any sub-frame objects have lost their connection to the renderer process. Commands can no longer be routed and will be discarded. - ICefLifeSpanHandler.OnBeforeClose => The browser has been destroyed. - ICefFrameHandler.OnFrameDetached => The main frame object have lost its connection to the renderer process. Notifications will be sent for any sub-frame objects before the main frame object. Commands can no longer be routed and will be discarded. - ICefFrameHandler.OnMainFrameChanged => The final main frame object has been removed from the browser.

Cross-origin navigation and/or loading receives special handling.

When the main frame navigates to a different origin the OnMainFrameChanged callback (2) will be executed with the old and new main frame objects.

When a new sub-frame is loaded in, or an existing sub-frame is navigated to, a different origin from the parent frame, a temporary sub-frame object will first be created in the parent's renderer process. That temporary sub-frame will then be discarded after the real cross-origin sub-frame is created in the new/target renderer process. The client will receive cross-origin navigation callbacks (2) for the transition from the temporary sub-frame to the real sub-frame. The temporary sub-frame will not recieve or execute commands during this transitional period (any sent commands will be discarded).

When a new popup browser is created in a different origin from the parent browser, a temporary main frame object for the popup will first be created in the parent's renderer process. That temporary main frame will then be discarded after the real cross-origin main frame is created in the new/target renderer process. The client will recieve creation and initial navigation callbacks (1) for the temporary main frame, followed by cross- origin navigation callbacks (2) for the transition from the temporary main frame to the real main frame. The temporary main frame may receive and execute commands during this transitional period (any sent commands may be executed, but the behavior is potentially undesirable since they execute in the parent browser's renderer process and not the new/target renderer process).

Callbacks will not be executed for placeholders that may be created during pre-commit navigation for sub-frames that do not yet exist in the renderer process. Placeholders will have ICefFrame.GetIdentifier() == -4.

The functions of this interface will be called on the UI thread unless otherwise indicated.

Container for a single image represented at different scale factors. All image representations should be the same size in density independent pixel (DIP) units. For example, if the image at scale factor 1.0 is 100x100 pixels then the image at scale factor 2.0 should be 200x200 pixels – both images will display with a DIP size of 100x100 units. The functions of this interface can be called on any browser process thread.

Implement this interface to handle events related to JavaScript dialogs. The functions of this interface will be called on the UI thread.

LabelButton is a button with optional text and/or icon. Methods must be called on the browser process UI thread unless otherwise indicated.

Implement this interface to handle events related to browser life span. The functions of this interface will be called on the UI thread unless otherwise indicated.

Implement this interface to handle events related to browser load status. The functions of this interface will be called on the browser process UI thread or render process main thread (TID_RENDERER).

Implement this interface to handle events related to media access permission requests. The functions of this interface will be called on the browser process UI thread.

Represents the route between a media source and sink. Instances of this object are created via ICefMediaRouter.CreateRoute and retrieved via ICefMediaObserver.OnRoutes. Contains the status and metadata of a routing operation. The functions of this interface may be called on any browser process thread unless otherwise indicated.

Supports discovery of and communication with media devices on the local network via the Cast and DIAL protocols. The functions of this interface may be called on any browser process thread unless otherwise indicated.

Callback interface for ICefMediaSink.GetDeviceInfo. The functions of this interface will be called on the browser process UI thread.

MenuButton is a button with optional text, icon and/or menu marker that shows a menu when clicked with the left mouse button. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.

Custom interface used to handle all the ICefMenuButtonDelegate events.

Supports creation and modification of menus. See TCefMenuId for the command ids that have default implementations. All user-defined command ids should be between MENU_ID_USER_FIRST and MENU_ID_USER_LAST. The functions of this interface can only be accessed on the browser process the UI thread.

Interface used to represent an entry in navigation history.

Controller for an overlay that contains a contents View added via ICefWindow.AddOverlayView. Methods exposed by this controller should be called in preference to functions of the same name exposed by the contents View unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.

Implement this interface to handle Panel events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.

Callback interface for ICefBrowserHost.PrintToPDF. The functions of this interface will be called on the browser process UI thread.

Callback interface used for asynchronous continuation of permission prompts.

Interface used to represent a single element in the request post data. The functions of this interface may be called on any thread.

Callback interface for asynchronous continuation of print dialog requests.

Callback interface for asynchronous continuation of print job requests.

Interface representing a message. Can be used on any process and thread.

Generic callback interface used for managing the lifespan of a registration.

Interface used to implement render process callbacks. The functions of this interface will be called on the render process main thread (TID_RENDERER) unless otherwise indicated.

A request context provides request handling for a set of related browser or URL request objects. A request context can be specified when creating a new browser via the ICefBrowserHost static factory functions or when creating a new URL request via the ICefUrlRequest static factory functions. Browser objects with different request contexts will never be hosted in the same render process. Browser objects with the same request context may or may not be hosted in the same render process depending on the process model. Browser objects created indirectly via the JavaScript window.open function or targeted links will share the same render process and the same request context as the source browser. When running in single-process mode there is only a single render process (the main process) and so all browsers created in single-process mode will share the same request context. This will be the first request context passed into a ICefBrowserHost static factory function and all other request context objects will be ignored.

Implement this interface to handle events related to browser requests. The functions of this interface will be called on the thread indicated.

Interface used for retrieving resources from the resource bundle (*.pak) files loaded by CEF during startup or via the ICefResourceBundleHandler returned from ICefApp.GetResourceBundleHandler. See TCefSettings for additional options related to resource bundle loading. The functions of this interface may be called on any thread unless otherwise indicated.

Interface used to implement a custom request handler interface. The functions of this interface will be called on the IO thread unless otherwise indicated.

Implement this interface to handle events related to browser requests. The functions of this interface will be called on the IO thread unless otherwise indicated.

Interface used to represent a web response. The functions of this interface may be called on any thread.

Callback interface used for continuation of custom context menu display.

Callback interface used for continuation of custom quick menu display.

A ScrollView will show horizontal and/or vertical scrollbars when necessary based on the size of the attached content view. Methods must be called on the browser process UI thread unless otherwise indicated.

Interface representing a server that supports HTTP and WebSocket requests. Server capacity is limited and is intended to handle only a small number of simultaneous connections (e.g. for communicating between applications on localhost). The functions of this interface are safe to call from any thread in the brower process unless otherwise indicated.

Interface to implement to be notified of asynchronous completion via ICefCookieManager.SetCookie.

Interface that builds a ICefProcessMessage containing a shared memory region. This interface is not thread-safe but may be used exclusively on a different thread from the one which constructed it.

Interface representing the SSL information for a navigation entry.

Interface used to write data to a stream. The functions of this interface may be called on any thread.

Custom interface used to handle all the CEF functions related to CefStringMap.

Implement this interface to receive string values asynchronously.

Interface that asynchronously executes tasks on the associated thread. It is safe to call the functions of this interface on any thread.

CEF maintains multiple internal threads that are used for handling different types of tasks in different processes. The TCefThreadId definitions in cef_types.h list the common CEF threads. Task runners are also available for other CEF threads as appropriate (for example, V8 WebWorker threads).

Implement this interface to handle Textfield events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.

A simple thread abstraction that establishes a message loop on a new thread. The consumer uses ICefTaskRunner to execute code on the thread's message loop. The thread is terminated when the ICefThread object is destroyed or stop() is called. All pending tasks queued on the thread's message loop will run to completion before the thread is terminated. cef_thread_create() can be called on any valid CEF thread in either the browser or render process. This interface should only be used for tasks that require a dedicated thread. In most cases you can post tasks to an existing CEF thread instead of creating a new one; see cef_task.h for details.

Interface that should be implemented by the ICefUrlRequest client. The functions of this interface will be called on the same thread that created the request unless otherwise documented.

Interface that should be implemented to handle V8 accessor calls. Accessor identifiers are registered by calling ICefV8value.SetValue(). The functions of this interface will be called on the thread associated with the V8 accessor.

Interface representing a V8 context handle. V8 handles can only be accessed from the thread on which they are created. Valid threads for creating a V8 handle include the render process main thread (TID_RENDERER) and WebWorker threads. A task runner for posting tasks on the associated thread can be retrieved via the ICefV8context.GetTaskRunner() function.

Interface that should be implemented to handle V8 function calls. The functions of this interface will be called on the thread associated with the V8 function.

Interface representing a V8 stack frame handle. V8 handles can only be accessed from the thread on which they are created. Valid threads for creating a V8 handle include the render process main thread (TID_RENDERER) and WebWorker threads. A task runner for posting tasks on the associated thread can be retrieved via the ICefv8context.GetTaskRunner() function.

Interface representing a V8 value handle. V8 handles can only be accessed from the thread on which they are created. Valid threads for creating a V8 handle include the render process main thread (TID_RENDERER) and WebWorker threads. A task runner for posting tasks on the associated thread can be retrieved via the ICefv8context.GetTaskRunner() function.

A View is a rectangle within the views View hierarchy. It is the base interface for all Views. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.

Custom interface used to handle the ICefViewDelegate events.

A Window is a top-level Window/widget in the Views hierarchy. By default it will have a non-client area with title bar, icon and buttons that supports moving and resizing. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.

Custom interface used to handle all the ICefWindowDelegate events.

Interface representing a X.509 certificate.

Interface that supports the reading of XML data via the libxml streaming API. The functions of this interface should only be called on the thread that creates the object.

Custom interface used to handle all the TChromiumCore events.

TBrowserWindow

A simple "drop on the Form" component for an full embedded browser.

The component handles most events required by CEF. The only additions needed to be made by the User in their code are:

* Implement TForm.OnCloseQuery CEF must be able to destroy the browser, before the main form is closed. (That is while the Form still has a Handle, and the event loop is still running) It is adviced to do the same for any other form (other than the main form).

TForm.OnCloseQuery should call (for each TBrowserWindow) TBrowserWindow.CloseBrowser(True); The Form can be allowed to close by setting (checking for all BrowserWindows) CanClose := BrowserWindow.IsClosed;

On Windows and Linux it is also possible to Destroy the TBrowserWindow. This will wait for the browser to close, and after that the form can be closed. - However, this must be done in OnCloseQuery (or before). - Once TForm.Destroy is called, it is to late. By that time the event loop no longer runs.

*** IMPORTANT: (MacOS) *** On MacOs CloseBrowser() must be called, and the *event* must be awaited. Neither destroying the component, nor waiting with App.ProcessMessages will work. On MacOS, CEF will not finish until the OnCloseQuery event returned to the main event loop. (Hence ProcessMessage does not work). The same is true for any action taken in OnClick or other event. CEF always waits for any event to return to the main event loop. See also the BrowserWindowEX example how that affect modal forms.

* Implement TBrowserWindow.OnBrowserClosed If TForm.OnCloseQuery called CloseBrowser, this callback can be used to call Form.Close again (the callback should check if the browser was closed by OnCloseQuery.

* On Windows: handle the WM_ENTERMENULOOP and WM_EXITMENULOOP, as shown in examples

* Optional prevent pop-up windows by implementing Chromium.BeforePopup Chromium.OpenUrlFromTab

Implement this structure to receive accessibility notification when accessibility events have been registered. The functions of this structure will be called on the UI thread.

Implement this structure to provide handler implementations. Methods will be called by the process and/or thread indicated.

Parent class of TCefApplication used to simplify the CEF initialization and destruction.

Callback structure used for asynchronous continuation of authentication requests.

All ref-counted framework structures must include this structure first.

The complete list of compiler versions is here : http://docwiki.embarcadero.com/RADStudio/Tokyo/en/Compiler_Versions Delphi 5 Delphi 6 Delphi 7 Delphi 8 Delphi 2005 Delphi 2009 Delphi 2010 Delphi XE Delphi XE2 (First FireMonkey and 64bit compiler) Delphi XE3 Delphi XE4 Delphi XE5 Delphi XE6 Delphi XE7 Delphi XE8 Rad Studio 10 - Delphi Seattle Rad Studio 10.1 - Delphi Berlin Rad Studio 10.2 - Delphi Tokyo Rad Studio 10.3 - Delphi Rio Rad Studio 10.4 - Delphi Sydney Rad Studio 11.0 - Delphi Alexandria Rad Studio 12.0 - Delphi Yukon Delphi uses MACOS for the new MacOSX and DARWIN is not defined FPC uses DARWIN for the new MacOSX and MACOS is defined for the classic Macintosh OS (System 7) We define MACOSX to avoid conflicts in both situations

Class that stores a copy of the raw bitmap buffer sent by CEF in the TChromiumCore.OnPaint event.

A Layout manager that arranges child views vertically or horizontally in a side-by-side fashion with spacing around and between the child views. The child views are always sized according to their preferred size. If the host's bounds provide insufficient space, child views will be clamped. Excess space will not be distributed. Methods must be called on the browser process UI thread unless otherwise indicated.

Structure used to represent a browser. When used in the browser process the functions of this structure may be called on any thread unless otherwise indicated in the comments. When used in the render process the functions of this structure may only be called on the main thread.

Structure used to represent the browser process aspects of a browser. The functions of this structure can only be called in the browser process. They may be called on any thread in that process unless otherwise indicated in the comments.

Browser initialization settings. Specify NULL or 0 to get the recommended default values. The consequences of using custom values may not be well tested. Many of these and other settings can also configured using command- line switches.

Component hosting a ICefBrowserView instance. Used in Chrome runtime mode only.

Implement this interface to handle BrowserView events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.

A View hosting a ICefBrowser instance. Methods must be called on the browser process UI thread unless otherwise indicated.

Implement this interface to handle Button events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.

A View representing a button. Depending on the specific type, the button could be implemented by a native control or custom rendered. Methods must be called on the browser process UI thread unless otherwise indicated.

Generic callback structure used for asynchronous continuation.

Custom class used to execute CEF tasks with a TChromiumCore component.

Structure representing IME composition underline information. This is a thin wrapper around Blink's WebCompositionUnderline class and should be kept in sync with that.

Implement this structure to filter cookies that may be sent or received from resource requests. The functions of this structure will be called on the IO thread unless otherwise indicated.

Structure representing cursor information. |buffer| will be |size.width|*|size.height|*4 bytes in size and represents a BGRA image with an upper-left origin.

CEF string maps are a set of key/value string pairs.

CEF string multimaps are a set of key/value string pairs. More than one value can be assigned to a single key.

This structure typically, but not always, corresponds to a physical display connected to the system. A fake Display may exist on a headless system, or a Display may correspond to a remote, virtual display. All size and position values are in density independent pixel (DIP) coordinates unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.

Event handler related to browser display state. The functions of this interface will be called on the UI thread.

Structure used to represent a DOM document. The functions of this structure should only be called on the render process main thread thread.

Structure used to represent a DOM node. The functions of this structure should only be called on the render process main thread.

Structure to implement for visiting the DOM. The functions of this structure will be called on the render process main thread.

Structure used to handle file downloads. The functions of this structure will called on the browser process UI thread.

Callback structure for ICefBrowserHost.DownloadImage. The functions of this structure will be called on the browser process UI thread.

Structure used to represent a download item.

Implement this structure to handle events related to dragging. The functions of this structure will be called on the UI thread.

Object representing an extension. Methods may be called on any thread unless otherwise indicated.

Callback structure for asynchronous continuation of file dialog requests.

A simple Layout that causes the associated Panel's one child to be sized to match the bounds of its parent. Methods must be called on the browser process UI thread unless otherwise indicated.

Implement this structure to handle events related to focus. The functions of this structure will be called on the UI thread.

Structure used to represent a frame in the browser window. When used in the browser process the functions of this structure may be called on any thread unless otherwise indicated in the comments. When used in the render process the functions of this structure may only be called on the main thread.

Callback structure used for asynchronous continuation of JavaScript dialog requests.

Implement this structure to handle events related to JavaScript dialogs. The functions of this structure will be called on the UI thread.

LabelButton is a button with optional text and/or icon. Methods must be called on the browser process UI thread unless otherwise indicated.

LabelButton is a button with optional text and/or icon. Methods must be called on the browser process UI thread unless otherwise indicated.

A Layout handles the sizing of the children of a Panel according to implementation-specific heuristics. Methods must be called on the browser process UI thread unless otherwise indicated.

This component can be used by VCL and LCL applications. It has the same purpose as TCEFWindowParent but it has a Chromium property to link it directly to a TChromium component. TCEFLinkedWindowParent resizes the child controls created by CEF for browsers in normal mode and sets the browser focus using the linked TChromium component. TCEFWindowParent and TCEFLinkedWindowParent work fine in Windows and you can used any of them but you can't use TCEFWindowParent in Linux or MacOS.

Custom class used to execute CEF tasks with CEF4Delphi components.

Callback structure for ICefMediaRouter.CreateRoute. The functions of this structure will be called on the browser process UI thread.

Custom record with media route information.

Represents a sink to which media can be routed. Instances of this object are retrieved via ICefMediaObserver.OnSinks. The functions of this structure may be called on any browser process thread unless otherwise indicated.

Callback structure for ICefMediaSink.GetDeviceInfo. The functions of this structure will be called on the browser process UI thread.

Custom record with media sink information.

Represents a source from which media can be routed. Instances of this object are retrieved via ICefMediaRouter.GetSource. The functions of this structure may be called on any browser process thread unless otherwise indicated.

Implement this interface to handle MenuButton events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.

MenuButton pressed lock is released when this object is destroyed.

MenuButton is a button with optional text, icon and/or menu marker that shows a menu when clicked with the left mouse button. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.

Implement this structure to handle menu model events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.

Structure used to represent an entry in navigation history.

Callback structure for ICefBrowserHost.GetNavigationEntries. The functions of this structure will be called on the browser process UI thread.

Controller for an overlay that contains a contents View added via ICefWindow.AddOverlayView. Methods exposed by this controller should be called in preference to functions of the same name exposed by the contents View unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.

A Panel is a container in the views hierarchy that can contain other Views as children. Methods must be called on the browser process UI thread unless otherwise indicated.

Implement this structure to handle Panel events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.

Callback structure for ICefBrowserHost.PrintToPDF. The functions of this structure will be called on the browser process UI thread.

Structure representing PDF print settings. These values match the parameters supported by the DevTools Page.printToPDF function. See https://chromedevtools.github.io/devtools-protocol/tot/Page/#method-printToPDF

Popup window features.

Structure used to represent a single element in the request post data. The functions of this structure may be called on any thread.

Manage access to preferences. Many built-in preferences are registered by Chromium. Custom preferences can be registered in ICefBrowserProcessHandler.OnRegisterCustomPreferences.

Structure that manages custom preference registrations.

Callback structure for asynchronous continuation of print dialog requests.

Implement this structure to handle printing on Linux. Each browser will have only one print job in progress at a time. The functions of this structure will be called on the browser process UI thread.

Callback structure for asynchronous continuation of print job requests.

Structure representing print settings.

Structure representing a message. Can be used on any process and thread.

Structure representing a range.

Generic callback structure used for managing the lifespan of a registration.

Implement this structure to handle events when window rendering is disabled. The functions of this structure will be called on the UI thread.

Structure used to implement render process callbacks. The functions of this structure will be called on the render process main thread (TID_RENDERER) unless otherwise indicated.

Structure used to represent a web request. The functions of this structure may be called on any thread.

Implement this structure to provide handler implementations. The handler instance will not be released until all objects related to the context have been destroyed.

Request context initialization settings. Specify NULL or 0 to get the recommended default values.

Callback structure for ICefRequestContext.ResolveHost.

Structure used for retrieving resources from the resource bundle (*.pak) files loaded by CEF during startup or via the ICefResourceBundleHandler returned from ICefApp.GetResourceBundleHandler. See TCefSettings for additional options related to resource bundle loading. The functions of this structure may be called on any thread unless otherwise indicated.

Structure used to implement a custom request handler structure. The functions of this structure will be called on the IO thread unless otherwise indicated.

Callback for asynchronous continuation of ICefResourceHandler.skip().

Structure used to represent a web response. The functions of this structure may be called on any thread.

Structure that creates ICefResourceHandler instances for handling scheme requests. The functions of this structure will always be called on the IO thread.

Structure that manages custom scheme registrations.

Screen information used when window rendering is disabled. This structure is passed as a parameter to ICefRenderHandler.GetScreenInfo and should be filled in by the client.

Callback structure used to select a client certificate for authentication.

TCEFSentinel is used as a timer that checks the number of running CEF processes when you close all browsers before shutdown. This component is only used as a last resort when there's an unresolved shutdown issue in CEF or CEF4Delphi that generates exceptions when the application is closed.

The TCEFServerComponent class puts together all CEF server procedures, functions, properties and events in one place.

Structure representing SSL information.

Structure representing the SSL information for a navigation entry.

Structure used to read data from a stream. The functions of this structure may be called on any thread.

Structure used to write data to a stream. The functions of this structure may be called on any thread.

CEF utf16 string type definition. Whomever allocates |str| is responsible for providing an appropriate |dtor| implementation that will free the string in the same memory space. When reusing an existing string structure make sure to call |dtor| for the old value before assigning new |str| and |dtor| values. Static strings will have a NULL |dtor| value. Using the below functions if you want this managed for you.

Implement this structure to receive string values asynchronously.

CEF wide string type definition. Whomever allocates |str| is responsible for providing an appropriate |dtor| implementation that will free the string in the same memory space. When reusing an existing string structure make sure to call |dtor| for the old value before assigning new |str| and |dtor| values. Static strings will have a NULL |dtor| value. Using the below functions if you want this managed for you.

Structure that asynchronously executes tasks on the associated thread. It is safe to call the functions of this structure on any thread.

CEF maintains multiple internal threads that are used for handling different types of tasks in different processes. The TCefThreadId definitions in cef_types.h list the common CEF threads. Task runners are also available for other CEF threads as appropriate (for example, V8 WebWorker threads).

A Textfield supports editing of text. This control is custom rendered with no platform-specific code. Methods must be called on the browser process UI thread unless otherwise indicated.

Implement this structure to handle Textfield events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.

A simple thread abstraction that establishes a message loop on a new thread. The consumer uses ICefTaskRunner to execute code on the thread's message loop. The thread is terminated when the ICefThread object is destroyed or stop() is called. All pending tasks queued on the thread's message loop will run to completion before the thread is terminated. cef_thread_create() can be called on any valid CEF thread in either the browser or render process. This structure should only be used for tasks that require a dedicated thread. In most cases you can post tasks to an existing CEF thread instead of creating a new one; see cef_task.h for details.

Time information. Values should always be in UTC.

Touch handle state.

URL component parts.

Structure that should be implemented by the ICefUrlRequest client. The functions of this structure will be called on the same thread that created the request unless otherwise documented.

Custom class used to execute CEF tasks with a TCEFUrlRequestClientComponent component.

Structure representing a V8 context handle. V8 handles can only be accessed from the thread on which they are created. Valid threads for creating a V8 handle include the render process main thread (TID_RENDERER) and WebWorker threads. A task runner for posting tasks on the associated thread can be retrieved via the ICefv8context.GetTaskRunner() function.

Structure representing a V8 exception. The functions of this structure may be called on any render process thread.

Structure that should be implemented to handle V8 function calls. The functions of this structure will be called on the thread associated with the V8 function.

Implement this interface to handle view events. All size and position values are in density independent pixels (DIP) unless otherwise indicated. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.

Custom class used to execute CEF tasks with a TCEFViewComponent component.

WaitableEvent is a thread synchronization tool that allows one thread to wait for another thread to finish some work. This is equivalent to using a Lock+ConditionVariable to protect a simple boolean value. However, using WaitableEvent in conjunction with a Lock to wait for a more complex state change (e.g., for an item to be added to a queue) is not recommended. In that case consider using a ConditionVariable instead of a WaitableEvent. It is safe to create and/or signal a WaitableEvent from any thread. Blocking on a WaitableEvent by calling the *wait() functions is not allowed on the browser process UI or IO threads.

Custom TWinControl used by CEF browsers.

Implement this interface to handle window events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.

Structure representing window information.

A Window is a top-level Window/widget in the Views hierarchy. By default it will have a non-client area with title bar, icon and buttons that supports moving and resizing. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.

Structure the client can implement to provide a custom stream writer. The functions of this structure may be called on any thread.

Structure representing a X.509 certificate.

Structure representing the issuer or subject field of an X.509 certificate.

Structure that supports the reading of XML data via the libxml streaming API. The functions of this structure should only be called on the thread that creates the object.

Structure that supports the reading of zip archives via the zlib unzip API. The functions of this structure should only be called on the thread that creates the object.

VCL and LCL version of TChromiumCore that puts together all browser procedures, functions, properties and events in one place. It has all you need to create, modify and destroy a web browser.

The TChromiumFontOptions properties are used to fill the TCefBrowserSettings record which is used during the browser creation.

This component puts together a TChromium and a TCEFWindowParent to embbed a web browser with only one component.

This component should only be used in extremely simple applications with simple browsers. In other cases it's recomended using a TChromium with a TCEFWindowParent as shown in the SimpleBrowser2 demo.

Cookie information.

This class handles all the ICefButtonDelegate methods which call the ICefButtonDelegateEvents methods. ICefButtonDelegateEvents will be implemented by the control receiving the ICefButtonDelegate events.

This class handles all the ICefPanelDelegate methods which call the ICefPanelDelegateEvents methods. ICefPanelDelegateEvents will be implemented by the control receiving the ICefPanelDelegate events.

This class handles all the ICefTextfieldDelegate and ICefViewDelegate methods which call the ICefTextfieldDelegateEvents methods. ICefTextfieldDelegateEvents will be implemented by the control receiving the ICefTextfieldDelegate events.

This class handles all the TCustomWindowDelegate methods which call the ICefWindowDelegateEvents methods. ICefWindowDelegateEvents will be implemented by the control receiving the TCustomWindowDelegate events.

TEmbeddedOsrChromium

Hides (THiddenPropertyEditor) any published event that is used by TOsrBrowserWindow * Hidden events must also not be used by user code *

TBufferPanel is used by FMX applications with browsers in OSR mode to draw the browser contents. See the FMXExternalPumpBrowser demo for more details.

Record used with RtlGetVersion to get the Windows version information.

String version of TCefUrlParts