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.
Represents a wall clock time in UTC. Values are not guaranteed to be
monotonically non-decreasing and are subject to large amounts of skew.
Time is stored internally as microseconds since the Windows epoch (1601).
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.
Structure used to implement browser process callbacks. The functions of this
structure will be called on the browser process main thread unless otherwise
indicated.
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.
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.
Implement this structure to handle BrowserView events. The functions of this
structure will be called on the browser process UI thread unless otherwise
indicated.
Structure used to create and/or parse command line arguments. Arguments with
“–”, “-” and, on Windows, “/” prefixes are considered switches. Switches
will always precede any arguments without switch prefixes. Switches can
optionally have a value specified using the “=” delimiter (e.g.
“-switch=value”). An argument of “–” will terminate switch parsing with all
subsequent tokens, regardless of prefix, being interpreted as non-switch
arguments. Switch names should be lowercase ASCII and will be converted to
such if necessary. Switch values will retain the original case and UTF8
encoding. This structure can be used before cef_initialize() is called.
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.
Callback structure for cef_browser_host_t::AddDevToolsMessageObserver. The
functions of this structure will be called on the browser process UI thread.
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.
Implement this structure to handle events related to browser extensions. The
functions of this structure will be called on the UI thread. See
cef_request_context_t::LoadExtension for information about extension
loading.
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.
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
structure can be called on any browser process thread.
Implement this structure to handle events related to browser life span. The
functions of this structure will be called on the UI thread unless otherwise
indicated.
Implement this structure to handle events related to browser load status.
The functions of this structure will be called on the browser process UI
thread or render process main thread (TID_RENDERER).
Implemented by the client to observe MediaRouter events and registered via
cef_media_router_t::AddObserver. The functions of this structure 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 cef_media_router_t::CreateRoute and retrieved via
cef_media_observer_t::OnRoutes. Contains the status and metadata of a
routing operation. The functions of this structure 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 structure may
be called on any browser process thread unless otherwise indicated.
Represents a sink to which media can be routed. Instances of this object are
retrieved via cef_media_observer_t::OnSinks. The functions of this structure
may be called on any browser process thread unless otherwise indicated.
Represents a source from which media can be routed. Instances of this object
are retrieved via cef_media_router_t::GetSource. The functions of this
structure may be called on any browser process 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.
Supports creation and modification of menus. See cef_menu_id_t 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 structure can only be accessed on the browser process the UI thread.
Controller for an overlay that contains a contents View added via
cef_window_t::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 structure to handle Panel events. The functions of this
structure will 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.
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
Implement this structure to handle events related to permission requests.
The functions of this structure will be called on the browser process UI
thread.
Manage access to preferences. Many built-in preferences are registered by
Chromium. Custom preferences can be registered in
cef_browser_process_handler_t::OnRegisterCustomPreferences.
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.
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.
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 cef_browser_host_t static factory functions or when creating
a new URL request via the cef_urlrequest_t 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 cef_browser_host_t static factory
function and all other request context objects will be ignored.
Structure used to implement a custom resource bundle structure. See
CefSettings for additional options related to resource bundle loading. The
functions of this structure may be called on multiple threads.
Structure used to implement a custom request handler structure. The
functions of this structure will be called on the IO thread unless otherwise
indicated.
Implement this structure to handle events related to browser requests. The
functions of this structure will be called on the IO thread unless otherwise
indicated.
Structure that creates cef_resource_handler_t instances for handling scheme
requests. The functions of this structure will always be called on the IO
thread.
Screen information used when window rendering is disabled. This structure is
passed as a parameter to CefRenderHandler::GetScreenInfo and should be
filled in by the client.
Initialization settings. Specify NULL or 0 to get the recommended default
values. Many of these and other settings can also configured using command-
line switches.
CEF string type definitions. 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 for asynchronous task execution. If the task is
posted successfully and if the associated message loop is still running then
the execute() function will be called on the target thread. If the task
fails to post then the task object may be destroyed on the source thread
instead of the target thread. For this reason be cautious when performing
work in the task object destructor.
Structure that should be implemented to handle V8 accessor calls. Accessor
identifiers are registered by calling cef_v8value_t::set_value(). The
functions of this structure will be called on the thread associated with the
V8 accessor.
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 cef_v8context_t::get_task_runner() function.
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.
Structure that should be implemented to handle V8 interceptor calls. The
functions of this structure will be called on the thread associated with the
V8 interceptor. Interceptor’s named property handlers (with first argument
of type CefString) are called when object is indexed by string. Indexed
property handlers (with first argument of type int) are called when object
is indexed by integer.
Structure 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 cef_v8context_t::get_task_runner() function.
Structure representing a V8 stack trace 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 cef_v8context_t::get_task_runner() function.
Structure 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 cef_v8context_t::get_task_runner() function.
Structure that wraps other data value types. Complex types (binary,
dictionary and list) will be referenced but not owned by this object. Can be
used on any process and thread.
Implement this structure to handle view events. All size and position values
are in density independent pixels (DIP) unless otherwise indicated. The
functions of this structure will be called on the browser process UI thread
unless otherwise indicated.
A View is a rectangle within the views View hierarchy. It is the base
structure 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.
Implement this structure to handle window events. The functions of this
structure will be called on the browser process UI thread unless otherwise
indicated.
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.
“Verb” of a drag-and-drop operation as negotiated between the source and
destination. These constants match their equivalents in WebCore’s
DragActions.h and should not be renumbered.
Supported certificate status code values. See net\cert\cert_status_flags.h
for more information. CERT_STATUS_NONE is new in CEF because we use an
enum while cert_status_flags.h uses a typedef and static const variables.
Enumerates the various representations of the ordering of audio channels.
Must be kept synchronized with media::ChannelLayout from Chromium.
See media\base\channel_layout.h
Supported content setting types. Some types are platform-specific or only
supported with the Chrome runtime. Should be kept in sync with Chromium’s
ContentSettingsType type.
Supported context menu edit state bit flags. These constants match their
equivalents in Chromium’s ContextMenuDataEditFlags and should not be
renumbered.
Supported context menu media state bit flags. These constants match their
equivalents in Chromium’s ContextMenuData::MediaFlags and should not be
renumbered.
Permission types used with OnShowPermissionPrompt. Some types are
platform-specific or only supported with the Chrome runtime. Should be kept
in sync with Chromium’s permissions::RequestType type.
Policy for how the Referrer HTTP header value will be sent during
navigation. If the --no-referrers command-line flag is specified then the
policy value will be ignored and the Referrer value will never be sent. Must
be kept synchronized with net::URLRequest::ReferrerPolicy from Chromium.
Supported UI scale factors for the platform. SCALE_FACTOR_NONE is used for
density independent resources such as string, html/js files or an image that
can be used for any scale factors (such as wallpapers).
Certificate types supported by CefTestServer::CreateAndStart. The matching
certificate file must exist in the “net/data/ssl/certificates” directory.
See CefSetDataDirectoryForTests() for related configuration.
Input mode of a virtual keyboard. These constants match their equivalents
in Chromium’s text_input_mode.h and should not be renumbered.
See https://html.spec.whatwg.org/#input-modalities:-the-inputmode-attribute
The manner in which a link click should be opened. These constants match
their equivalents in Chromium’s window_open_disposition.h and should not be
renumbered.
Supported XML encoding types. The parser supports ASCII, ISO-8859-1, and
UTF16 (LE and BE) by default. All other types must be translated to UTF8
before being passed to the parser. If a BOM is detected and the correct
decoder is available then that decoder will be used automatically.
Create a new browser using the window parameters specified by |windowInfo|.
All values will be copied internally and the actual window (if any) will be
created on the UI thread. If |request_context| is NULL the global request
context will be used. This function can be called on any browser process
thread and will not block. The optional |extra_info| parameter provides an
opportunity to specify extra information specific to the created browser
that will be passed to cef_render_process_handler_t::on_browser_created() in
the render process.
Create a new browser using the window parameters specified by |windowInfo|.
If |request_context| is NULL the global request context will be used. This
function can only be called on the browser process UI thread. The optional
|extra_info| parameter provides an opportunity to specify extra information
specific to the created browser that will be passed to
cef_render_process_handler_t::on_browser_created() in the render process.
Create a new BrowserView. The underlying cef_browser_t will not be created
until this view is added to the views hierarchy. The optional |extra_info|
parameter provides an opportunity to specify extra information specific to
the created browser that will be passed to
cef_render_process_handler_t::on_browser_created() in the render process.
Clear all scheme handler factories registered with the global request
context. Returns false (0) on error. This function may be called on any
thread in the browser process. Using this function is equivalent to calling
cef_request_context_t::cef_request_context_get_global_context()->clear_schem
e_handler_factories().
Returns the global cookie manager. By default data will be stored at
cef_settings_t.cache_path if specified or in memory otherwise. If |callback|
is non-NULL it will be executed asnychronously on the UI thread after the
manager’s storage has been initialized. Using this function is equivalent to
calling cef_request_context_t::cef_request_context_get_global_context()->Get
DefaultCookieManager().
Returns the Display that most closely intersects |bounds|. Set
|input_pixel_coords| to true (1) if |bounds| is in pixel screen coordinates
instead of DIP screen coordinates.
Perform a single iteration of CEF message loop processing. This function is
provided for cases where the CEF message loop must be integrated into an
existing application message loop. Use of this function is not recommended
for most users; use either the cef_run_message_loop() function or
cef_settings_t.multi_threaded_message_loop if possible. When using this
function care must be taken to balance performance against excessive CPU
usage. It is recommended to enable the cef_settings_t.external_message_pump
option when using this function so that
cef_browser_process_handler_t::on_schedule_message_pump_work() callbacks can
facilitate the scheduling process. This function should only be called on
the main application thread and only if cef_initialize() is called with a
cef_settings_t.multi_threaded_message_loop value of false (0). This function
will not block.
This function should be called from the application entry point function to
execute a secondary process. It can be used to run secondary processes from
the browser client executable (default behavior) or from a separate
executable specified by the cef_settings_t.browser_subprocess_path value. If
called for the browser process (identified by no “type” command-line value)
it will return immediately with a value of -1. If called for a recognized
secondary process it will block until the process should exit and then
return the process exit code. The |application| parameter may be NULL. The
|windows_sandbox_info| parameter is only used on Windows and may be NULL
(see cef_sandbox_win.h for details).
This function should be called on the main application thread to initialize
the CEF browser process. The |application| parameter may be NULL. A return
value of true (1) indicates that it succeeded and false (0) indicates that
it failed. The |windows_sandbox_info| parameter is only used on Windows and
may be NULL (see cef_sandbox_win.h for details).
Returns the MediaRouter object associated with the global request context.
If |callback| is non-NULL it will be executed asnychronously on the UI
thread after the manager’s storage has been initialized. Equivalent to
calling cef_request_context_t::cef_request_context_get_global_context()->get
_media_router().
Post a task for delayed execution on the specified thread. Equivalent to
using cef_task_runner_t::GetForThread(threadId)->PostDelayedTask(task,
delay_ms).
Quit the CEF message loop that was started by calling
cef_run_message_loop(). This function should only be called on the main
application thread and only if cef_run_message_loop() was used.
Register a new V8 extension with the specified JavaScript extension code and
handler. Functions implemented by the handler are prototyped using the
keyword ‘native’. The calling of a native function is restricted to the
scope in which the prototype of the native function is defined. This
function may only be called on the render process main thread.
Register a scheme handler factory with the global request context. An NULL
|domain_name| value for a standard scheme will cause the factory to match
all domain names. The |domain_name| value will be ignored for non-standard
schemes. If |scheme_name| is a built-in scheme and no handler is returned by
|factory| then the built-in scheme handler factory will be called. If
|scheme_name| is a custom scheme then you must also implement the
cef_app_t::on_register_custom_schemes() function in all processes. This
function may be called multiple times to change or remove the factory that
matches the specified |scheme_name| and optional |domain_name|. Returns
false (0) if an error occurs. This function may be called on any thread in
the browser process. Using this function is equivalent to calling cef_reques
t_context_t::cef_request_context_get_global_context()->register_scheme_handl
er_factory().
Run the CEF message loop. Use this function instead of an application-
provided message loop to get the best balance between performance and CPU
usage. This function should only be called on the main application thread
and only if cef_initialize() is called with a
cef_settings_t.multi_threaded_message_loop value of false (0). This function
will block until a quit message is received by the system.
These functions convert an ASCII string, typically a hardcoded constant, to
a Wide/UTF16 string. Use instead of the UTF8 conversion routines if you know
the string is ASCII.
Append a new key/value pair at the end of the string map. If the key exists,
overwrite the existing value with a new value w/o changing the pair order.
These functions set string values. If |copy| is true (1) the value will be
copied instead of referenced. It is up to the user to properly manage
the lifespan of references.
These functions convert between UTF-8, -16, and -32 strings. They are
potentially slow so unnecessary conversions should be avoided. The best
possible result will always be written to |output| with the boolean return
value indicating whether the conversion is 100% valid.
Returns the task runner for the current thread. Only CEF threads will have
task runners. An NULL reference will be returned if this function is called
on an invalid thread.
Converts cef_time_t to/from a double which is the number of seconds since
epoch (Jan 1, 1970). Webkit uses this format to represent time. A value of 0
means “not initialized”. Returns true (1) on success and false (0) on
failure.
Create a new cef_v8value_t object of type array with the specified |length|.
If |length| is negative the returned array will have length 0. This function
should only be called from within the scope of a
cef_render_process_handler_t, cef_v8handler_t or cef_v8accessor_t callback,
or in combination with calling enter() and exit() on a stored
cef_v8context_t reference.
Create a new cef_v8value_t object of type ArrayBuffer which wraps the
provided |buffer| of size |length| bytes. The ArrayBuffer is externalized,
meaning that it does not own |buffer|. The caller is responsible for freeing
|buffer| when requested via a call to
cef_v8array_buffer_release_callback_t::ReleaseBuffer. This function should
only be called from within the scope of a cef_render_process_handler_t,
cef_v8handler_t or cef_v8accessor_t callback, or in combination with calling
enter() and exit() on a stored cef_v8context_t reference.
Create a new cef_v8value_t object of type Date. This function should only be
called from within the scope of a cef_render_process_handler_t,
cef_v8handler_t or cef_v8accessor_t callback, or in combination with calling
enter() and exit() on a stored cef_v8context_t reference.
Create a new cef_v8value_t object of type function. This function should
only be called from within the scope of a cef_render_process_handler_t,
cef_v8handler_t or cef_v8accessor_t callback, or in combination with calling
enter() and exit() on a stored cef_v8context_t reference.
Create a new cef_v8value_t object of type object with optional accessor
and/or interceptor. This function should only be called from within the
scope of a cef_render_process_handler_t, cef_v8handler_t or cef_v8accessor_t
callback, or in combination with calling enter() and exit() on a stored
cef_v8context_t reference.
Create a new cef_v8value_t object of type Promise. This function should only
be called from within the scope of a cef_render_process_handler_t,
cef_v8handler_t or cef_v8accessor_t callback, or in combination with calling
enter() and exit() on a stored cef_v8context_t reference.
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.
Represents a wall clock time in UTC. Values are not guaranteed to be
monotonically non-decreasing and are subject to large amounts of skew.
Time is stored internally as microseconds since the Windows epoch (1601).
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.
Structure used to implement browser process callbacks. The functions of this
structure will be called on the browser process main thread unless otherwise
indicated.
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.
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.
Implement this structure to handle BrowserView events. The functions of this
structure will be called on the browser process UI thread unless otherwise
indicated.
Structure used to create and/or parse command line arguments. Arguments with
“–”, “-” and, on Windows, “/” prefixes are considered switches. Switches
will always precede any arguments without switch prefixes. Switches can
optionally have a value specified using the “=” delimiter (e.g.
“-switch=value”). An argument of “–” will terminate switch parsing with all
subsequent tokens, regardless of prefix, being interpreted as non-switch
arguments. Switch names should be lowercase ASCII and will be converted to
such if necessary. Switch values will retain the original case and UTF8
encoding. This structure can be used before cef_initialize() is called.
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.
Callback structure for cef_browser_host_t::AddDevToolsMessageObserver. The
functions of this structure will be called on the browser process UI thread.
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.
Implement this structure to handle events related to browser extensions. The
functions of this structure will be called on the UI thread. See
cef_request_context_t::LoadExtension for information about extension
loading.
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.
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
structure can be called on any browser process thread.
Implement this structure to handle events related to browser life span. The
functions of this structure will be called on the UI thread unless otherwise
indicated.
Implement this structure to handle events related to browser load status.
The functions of this structure will be called on the browser process UI
thread or render process main thread (TID_RENDERER).
Implemented by the client to observe MediaRouter events and registered via
cef_media_router_t::AddObserver. The functions of this structure 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 cef_media_router_t::CreateRoute and retrieved via
cef_media_observer_t::OnRoutes. Contains the status and metadata of a
routing operation. The functions of this structure 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 structure may
be called on any browser process thread unless otherwise indicated.
Represents a sink to which media can be routed. Instances of this object are
retrieved via cef_media_observer_t::OnSinks. The functions of this structure
may be called on any browser process thread unless otherwise indicated.
Represents a source from which media can be routed. Instances of this object
are retrieved via cef_media_router_t::GetSource. The functions of this
structure may be called on any browser process 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.
Supports creation and modification of menus. See cef_menu_id_t 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 structure can only be accessed on the browser process the UI thread.
Controller for an overlay that contains a contents View added via
cef_window_t::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 structure to handle Panel events. The functions of this
structure will 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.
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
Implement this structure to handle events related to permission requests.
The functions of this structure will be called on the browser process UI
thread.
Manage access to preferences. Many built-in preferences are registered by
Chromium. Custom preferences can be registered in
cef_browser_process_handler_t::OnRegisterCustomPreferences.
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.
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.
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 cef_browser_host_t static factory functions or when creating
a new URL request via the cef_urlrequest_t 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 cef_browser_host_t static factory
function and all other request context objects will be ignored.
Structure used to implement a custom resource bundle structure. See
CefSettings for additional options related to resource bundle loading. The
functions of this structure may be called on multiple threads.
Structure used to implement a custom request handler structure. The
functions of this structure will be called on the IO thread unless otherwise
indicated.
Implement this structure to handle events related to browser requests. The
functions of this structure will be called on the IO thread unless otherwise
indicated.
Structure that creates cef_resource_handler_t instances for handling scheme
requests. The functions of this structure will always be called on the IO
thread.
Screen information used when window rendering is disabled. This structure is
passed as a parameter to CefRenderHandler::GetScreenInfo and should be
filled in by the client.
Initialization settings. Specify NULL or 0 to get the recommended default
values. Many of these and other settings can also configured using command-
line switches.
It is sometimes necessary for the system to allocate string structures with
the expectation that the user will free them. The userfree types act as a
hint that the user is responsible for freeing the structure.
CEF string type definitions. 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 for asynchronous task execution. If the task is
posted successfully and if the associated message loop is still running then
the execute() function will be called on the target thread. If the task
fails to post then the task object may be destroyed on the source thread
instead of the target thread. For this reason be cautious when performing
work in the task object destructor.
Structure that should be implemented to handle V8 accessor calls. Accessor
identifiers are registered by calling cef_v8value_t::set_value(). The
functions of this structure will be called on the thread associated with the
V8 accessor.
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 cef_v8context_t::get_task_runner() function.
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.
Structure that should be implemented to handle V8 interceptor calls. The
functions of this structure will be called on the thread associated with the
V8 interceptor. Interceptor’s named property handlers (with first argument
of type CefString) are called when object is indexed by string. Indexed
property handlers (with first argument of type int) are called when object
is indexed by integer.
Structure 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 cef_v8context_t::get_task_runner() function.
Structure representing a V8 stack trace 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 cef_v8context_t::get_task_runner() function.
Structure 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 cef_v8context_t::get_task_runner() function.
Structure that wraps other data value types. Complex types (binary,
dictionary and list) will be referenced but not owned by this object. Can be
used on any process and thread.
Implement this structure to handle view events. All size and position values
are in density independent pixels (DIP) unless otherwise indicated. The
functions of this structure will be called on the browser process UI thread
unless otherwise indicated.
A View is a rectangle within the views View hierarchy. It is the base
structure 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.
Implement this structure to handle window events. The functions of this
structure will be called on the browser process UI thread unless otherwise
indicated.
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.