Crate cef_sys

Structs

• _XDisplay
• _XEvent
• _cef_accessibility_handler_t
  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.
• _cef_app_t
  Implement this structure to provide handler implementations. Methods will be called by the process and/or thread indicated.
• _cef_audio_handler_t
  Implement this structure to handle audio events.
• _cef_audio_parameters_t
  Structure representing the audio parameters for setting up the audio handler.
• _cef_auth_callback_t
  Callback structure used for asynchronous continuation of authentication requests.
• _cef_base_ref_counted_t
• _cef_base_scoped_t
• _cef_basetime_t
  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).
• _cef_before_download_callback_t
  Callback structure used to asynchronously continue a download.
• _cef_binary_value_t
  Structure representing a binary value. Can be used on any process and thread.
• _cef_box_layout_settings_t
  Settings used when initializing a CefBoxLayout.
• _cef_box_layout_t
• _cef_browser_host_t
  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.
• _cef_browser_process_handler_t
  Structure used to implement browser process callbacks. The functions of this structure will be called on the browser process main thread unless otherwise indicated.
• _cef_browser_settings_t
  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.
• _cef_browser_t
  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.
• _cef_browser_view_delegate_t
  Implement this structure to handle BrowserView events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
• _cef_browser_view_t
  A View hosting a cef_browser_t instance. Methods must be called on the browser process UI thread unless otherwise indicated.
• _cef_button_t
• _cef_callback_t
  Generic callback structure used for asynchronous continuation.
• _cef_client_t
  Implement this structure to provide handler implementations.
• _cef_command_handler_t
  Implement this structure to handle events related to commands. The functions of this structure will be called on the UI thread.
• _cef_command_line_t
  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.
• _cef_completion_callback_t
  Generic callback structure used for asynchronous completion.
• _cef_composition_underline_t
  Structure representing IME composition underline information. This is a thin wrapper around Blink’s WebCompositionUnderline class and should be kept in sync with that.
• _cef_context_menu_handler_t
  Implement this structure to handle context menu events. The functions of this structure will be called on the UI thread.
• _cef_context_menu_params_t
  Provides information about the context menu state. The functions of this structure can only be accessed on browser process the UI thread.
• _cef_cookie_access_filter_t
  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.
• _cef_cookie_manager_t
  Structure used for managing cookies. The functions of this structure may be called on any thread unless otherwise indicated.
• _cef_cookie_t
  Cookie information.
• _cef_cookie_visitor_t
  Structure to implement for visiting cookie values. The functions of this structure will always be called on the UI thread.
• _cef_cursor_info_t
  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_delete_cookies_callback_t
  Structure to implement to be notified of asynchronous completion via cef_cookie_manager_t::delete_cookies().
• _cef_dev_tools_message_observer_t
  Callback structure for cef_browser_host_t::AddDevToolsMessageObserver. The functions of this structure will be called on the browser process UI thread.
• _cef_dialog_handler_t
  Implement this structure to handle dialog events. The functions of this structure will be called on the browser process UI thread.
• _cef_dictionary_value_t
  Structure representing a dictionary value. Can be used on any process and thread.
• _cef_display_handler_t
  Implement this structure to handle events related to browser display state. The functions of this structure will be called on the UI thread.
• _cef_display_t
  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.
• _cef_domdocument_t
  Structure used to represent a DOM document. The functions of this structure should only be called on the render process main thread thread.
• _cef_domnode_t
  Structure used to represent a DOM node. The functions of this structure should only be called on the render process main thread.
• _cef_domvisitor_t
  Structure to implement for visiting the DOM. The functions of this structure will be called on the render process main thread.
• _cef_download_handler_t
  Structure used to handle file downloads. The functions of this structure will called on the browser process UI thread.
• _cef_download_image_callback_t
  Callback structure for cef_browser_host_t::DownloadImage. The functions of this structure will be called on the browser process UI thread.
• _cef_download_item_callback_t
  Callback structure used to asynchronously cancel a download.
• _cef_download_item_t
  Structure used to represent a download item.
• _cef_drag_data_t
  Structure used to represent drag data. The functions of this structure may be called on any thread.
• _cef_drag_handler_t
  Implement this structure to handle events related to dragging. The functions of this structure will be called on the UI thread.
• _cef_draggable_region_t
  Structure representing a draggable region.
• _cef_extension_handler_t
  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.
• _cef_extension_t
  Object representing an extension. Methods may be called on any thread unless otherwise indicated.
• _cef_file_dialog_callback_t
  Callback structure for asynchronous continuation of file dialog requests.
• _cef_fill_layout_t
• _cef_find_handler_t
  Implement this structure to handle events related to find results. The functions of this structure will be called on the UI thread.
• _cef_focus_handler_t
  Implement this structure to handle events related to focus. The functions of this structure will be called on the UI thread.
• _cef_frame_handler_t
  Implement this structure to handle events related to cef_frame_t life span. The order of callbacks is:
• _cef_frame_t
  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.
• _cef_get_extension_resource_callback_t
  Callback structure used for asynchronous continuation of cef_extension_handler_t::GetExtensionResource.
• _cef_image_t
  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.
• _cef_insets_t
  Structure representing insets.
• _cef_jsdialog_callback_t
  Callback structure used for asynchronous continuation of JavaScript dialog requests.
• _cef_jsdialog_handler_t
  Implement this structure to handle events related to JavaScript dialogs. The functions of this structure will be called on the UI thread.
• _cef_key_event_t
  Structure representing keyboard event information.
• _cef_keyboard_handler_t
  Implement this structure to handle events related to keyboard input. The functions of this structure will be called on the UI thread.
• _cef_layout_t
• _cef_life_span_handler_t
  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.
• _cef_list_value_t
  Structure representing a list value. Can be used on any process and thread.
• _cef_load_handler_t
  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).
• _cef_main_args_t
  Structure representing CefExecuteProcess arguments.
• _cef_media_access_callback_t
  Callback structure used for asynchronous continuation of media access permission requests.
• _cef_media_observer_t
  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.
• _cef_media_route_create_callback_t
  Callback structure for cef_media_router_t::CreateRoute. The functions of this structure will be called on the browser process UI thread.
• _cef_media_route_t
  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.
• _cef_media_router_t
  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.
• _cef_media_sink_device_info_callback_t
  Callback structure for cef_media_sink_t::GetDeviceInfo. The functions of this structure will be called on the browser process UI thread.
• _cef_media_sink_device_info_t
  Device information for a MediaSink object.
• _cef_media_sink_t
  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.
• _cef_media_source_t
  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.
• _cef_menu_model_delegate_t
  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.
• _cef_menu_model_t
  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.
• _cef_mouse_event_t
  Structure representing mouse event information.
• _cef_navigation_entry_t
  Structure used to represent an entry in navigation history.
• _cef_navigation_entry_visitor_t
  Callback structure for cef_browser_host_t::GetNavigationEntries. The functions of this structure will be called on the browser process UI thread.
• _cef_overlay_controller_t
  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.
• _cef_panel_delegate_t
  Implement this structure to handle Panel events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
• _cef_panel_t
  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.
• _cef_pdf_print_callback_t
  Callback structure for cef_browser_host_t::PrintToPDF. The functions of this structure will be called on the browser process UI thread.
• _cef_pdf_print_settings_t
  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
• _cef_permission_handler_t
  Implement this structure to handle events related to permission requests. The functions of this structure will be called on the browser process UI thread.
• _cef_permission_prompt_callback_t
  Callback structure used for asynchronous continuation of permission prompts.
• _cef_point_t
  Structure representing a point.
• _cef_popup_features_t
  Popup window features.
• _cef_post_data_element_t
  Structure used to represent a single element in the request post data. The functions of this structure may be called on any thread.
• _cef_post_data_t
  Structure used to represent post data for a web request. The functions of this structure may be called on any thread.
• _cef_preference_manager_t
  Manage access to preferences. Many built-in preferences are registered by Chromium. Custom preferences can be registered in cef_browser_process_handler_t::OnRegisterCustomPreferences.
• _cef_preference_registrar_t
  Structure that manages custom preference registrations.
• _cef_print_dialog_callback_t
  Callback structure for asynchronous continuation of print dialog requests.
• _cef_print_handler_t
  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.
• _cef_print_job_callback_t
  Callback structure for asynchronous continuation of print job requests.
• _cef_print_settings_t
  Structure representing print settings.
• _cef_process_message_t
  Structure representing a message. Can be used on any process and thread.
• _cef_range_t
  Structure representing a range.
• _cef_read_handler_t
  Structure the client can implement to provide a custom stream reader. The functions of this structure may be called on any thread.
• _cef_rect_t
  Structure representing a rectangle.
• _cef_registration_t
  Generic callback structure used for managing the lifespan of a registration.
• _cef_render_handler_t
  Implement this structure to handle events when window rendering is disabled. The functions of this structure will be called on the UI thread.
• _cef_render_process_handler_t
  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.
• _cef_request_context_handler_t
• _cef_request_context_settings_t
  Request context initialization settings. Specify NULL or 0 to get the recommended default values.
• _cef_request_context_t
  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.
• _cef_request_handler_t
  Implement this structure to handle events related to browser requests. The functions of this structure will be called on the thread indicated.
• _cef_request_t
  Structure used to represent a web request. The functions of this structure may be called on any thread.
• _cef_resolve_callback_t
  Callback structure for cef_request_context_t::ResolveHost.
• _cef_resource_bundle_handler_t
  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.
• _cef_resource_handler_t
  Structure used to implement a custom request handler structure. The functions of this structure will be called on the IO thread unless otherwise indicated.
• _cef_resource_read_callback_t
  Callback for asynchronous continuation of cef_resource_handler_t::read().
• _cef_resource_request_handler_t
  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.
• _cef_resource_skip_callback_t
  Callback for asynchronous continuation of cef_resource_handler_t::skip().
• _cef_response_filter_t
  Implement this structure to filter resource response content. The functions of this structure will be called on the browser process IO thread.
• _cef_response_t
  Structure used to represent a web response. The functions of this structure may be called on any thread.
• _cef_run_context_menu_callback_t
  Callback structure used for continuation of custom context menu display.
• _cef_run_file_dialog_callback_t
  Callback structure for cef_browser_host_t::RunFileDialog. The functions of this structure will be called on the browser process UI thread.
• _cef_run_quick_menu_callback_t
  Callback structure used for continuation of custom quick menu display.
• _cef_scheme_handler_factory_t
  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.
• _cef_scheme_registrar_t
  Structure that manages custom scheme registrations.
• _cef_screen_info_t
  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.
• _cef_scroll_view_t
• _cef_select_client_certificate_callback_t
  Callback structure used to select a client certificate for authentication.
• _cef_set_cookie_callback_t
  Structure to implement to be notified of asynchronous completion via cef_cookie_manager_t::set_cookie().
• _cef_settings_t
  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_shared_memory_region_t
  Structure that wraps platform-dependent share memory region mapping.
• _cef_size_t
  Structure representing a size.
• _cef_sslinfo_t
  Structure representing SSL information.
• _cef_sslstatus_t
  Structure representing the SSL information for a navigation entry.
• _cef_stream_reader_t
  Structure used to read data from a stream. The functions of this structure may be called on any thread.
• _cef_stream_writer_t
  Structure used to write data to a stream. The functions of this structure may be called on any thread.
• _cef_string_list_t
• _cef_string_map_t
• _cef_string_multimap_t
• _cef_string_utf8_t
• _cef_string_utf16_t
• _cef_string_visitor_t
  Implement this structure to receive string values asynchronously.
• _cef_string_wide_t
  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.
• _cef_task_runner_t
  Structure that asynchronously executes tasks on the associated thread. It is safe to call the functions of this structure on any thread.
• _cef_task_t
  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.
• _cef_textfield_t
• _cef_time_t
  Time information. Values should always be in UTC.
• _cef_touch_event_t
  Structure representing touch event information.
• _cef_touch_handle_state_t
• _cef_urlparts_t
  URL component parts.
• _cef_urlrequest_client_t
• _cef_urlrequest_t
• _cef_v8accessor_t
  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.
• _cef_v8array_buffer_release_callback_t
  Callback structure that is passed to cef_v8value_t::CreateArrayBuffer.
• _cef_v8context_t
  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.
• _cef_v8exception_t
  Structure representing a V8 exception. The functions of this structure may be called on any render process thread.
• _cef_v8handler_t
  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.
• _cef_v8interceptor_t
  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.
• _cef_v8stack_frame_t
  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.
• _cef_v8stack_trace_t
  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.
• _cef_v8value_t
  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.
• _cef_value_t
  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.
• _cef_view_delegate_t
  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.
• _cef_view_t
  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.
• _cef_window_delegate_t
  Implement this structure to handle window events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
• _cef_window_info_t
  Class representing window information.
• _cef_window_t
  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.
• _cef_write_handler_t
  Structure the client can implement to provide a custom stream writer. The functions of this structure may be called on any thread.
• _cef_x509cert_principal_t
  Structure representing the issuer or subject field of an X.509 certificate.
• _cef_x509certificate_t
  Structure representing a X.509 certificate.
• cef_drag_operations_mask_t
  “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.

Enums

• cef_alpha_type_t
  Describes how to interpret the alpha component of a pixel.
• cef_button_state_t
  Specifies the button display state.
• cef_cert_status_t
  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.
• cef_channel_layout_t
  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
• cef_chrome_page_action_icon_type_t
  Chrome page action icon types. Should be kept in sync with Chromium’s PageActionIconType type.
• cef_chrome_toolbar_button_type_t
  Chrome toolbar button types. Should be kept in sync with CEF’s internal ToolbarButtonType type.
• cef_chrome_toolbar_type_t
  Chrome toolbar types.
• cef_color_model_t
  Print job color mode values.
• cef_color_type_t
  Describes how to interpret the components of a pixel.
• cef_com_init_mode_t
  Windows COM initialization mode. Specifies how COM will be initialized for a new thread.
• cef_composition_underline_style_t
  Composition underline style.
• cef_content_setting_types_t
  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.
• cef_content_setting_values_t
  Supported content setting values. Should be kept in sync with Chromium’s ContentSetting type.
• cef_context_menu_edit_state_flags_t
  Supported context menu edit state bit flags. These constants match their equivalents in Chromium’s ContextMenuDataEditFlags and should not be renumbered.
• cef_context_menu_media_state_flags_t
  Supported context menu media state bit flags. These constants match their equivalents in Chromium’s ContextMenuData::MediaFlags and should not be renumbered.
• cef_context_menu_media_type_t
  Supported context menu media types. These constants match their equivalents in Chromium’s ContextMenuDataMediaType and should not be renumbered.
• cef_context_menu_type_flags_t
  Supported context menu type flags.
• cef_cookie_priority_t
  Cookie priority values.
• cef_cookie_same_site_t
  Cookie same site values.
• cef_cross_axis_alignment_t
  Specifies where along the cross axis the CefBoxLayout child views should be laid out.
• cef_cursor_type_t
  Cursor type values.
• cef_docking_mode_t
  Docking modes supported by CefWindow::AddOverlay.
• cef_dom_document_type_t
  DOM document types.
• cef_dom_event_category_t
  DOM event category flags.
• cef_dom_event_phase_t
  DOM event processing phases.
• cef_dom_node_type_t
  DOM node types.
• cef_download_interrupt_reason_t
  Download interrupt reasons. Should be kept in sync with Chromium’s download::DownloadInterruptReason type.
• cef_duplex_mode_t
  Print job duplex mode values.
• cef_errorcode_t
  Supported error code values. For the complete list of error values see “include/base/internal/cef_net_error_list.h”.
• cef_event_flags_t
  Supported event bit flags.
• cef_file_dialog_mode_t
  Supported file dialog modes.
• cef_focus_source_t
  Focus sources.
• cef_gesture_command_t
  Specifies the gesture commands.
• cef_horizontal_alignment_t
  Specifies the horizontal text alignment mode.
• cef_jsdialog_type_t
  Supported JavaScript dialog types.
• cef_json_parser_options_t
  Options that can be passed to CefParseJSON.
• cef_json_writer_options_t
  Options that can be passed to CefWriteJSON.
• cef_key_event_type_t
  Key event types.
• cef_log_items_t
  Log items prepended to each log line.
• cef_log_severity_t
  Log severity levels.
• cef_main_axis_alignment_t
  Specifies where along the main axis the CefBoxLayout child views should be laid out.
• cef_media_access_permission_types_t
  Media access permissions used by OnRequestMediaAccessPermission.
• cef_media_route_connection_state_t
  Connection state for a MediaRoute object.
• cef_media_route_create_result_t
  Result codes for CefMediaRouter::CreateRoute. Should be kept in sync with Chromium’s media_router::mojom::RouteRequestResultCode type.
• cef_media_sink_icon_type_t
  Icon types for a MediaSink object. Should be kept in sync with Chromium’s media_router::SinkIconType type.
• cef_menu_anchor_position_t
  Specifies how a menu will be anchored for non-RTL languages. The opposite position will be used for RTL languages.
• cef_menu_color_type_t
  Supported color types for menu items.
• cef_menu_id_t
  Supported menu IDs. Non-English translations can be provided for the IDS_MENU_* strings in CefResourceBundleHandler::GetLocalizedString().
• cef_menu_item_type_t
  Supported menu item types.
• cef_message_loop_type_t
  Message loop types. Indicates the set of asynchronous events that a message loop can process.
• cef_mouse_button_type_t
  Mouse button types.
• cef_navigation_type_t
  Navigation types.
• cef_paint_element_type_t
  Paint element types.
• cef_path_key_t
  Path key values.
• cef_pdf_print_margin_type_t
  Margin type for PDF printing.
• cef_permission_request_result_t
  Permission request results.
• cef_permission_request_types_t
  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.
• cef_pointer_type_t
  The device type that caused the event.
• cef_postdataelement_type_t
  Post data elements may represent either bytes or files.
• cef_preferences_type_t
  Preferences type passed to CefBrowserProcessHandler::OnRegisterCustomPreferences.
• cef_process_id_t
  Existing process IDs.
• cef_quick_menu_edit_state_flags_t
  Supported quick menu state bit flags.
• cef_referrer_policy_t
  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.
• cef_resource_type_t
  Resource type for a request. These constants match their equivalents in Chromium’s ResourceType and should not be renumbered.
• cef_response_filter_status_t
  Return values for CefResponseFilter::Filter().
• cef_return_value_t
  Return value types.
• cef_scale_factor_t
  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).
• cef_scheme_options_t
  Configuration options for registering a custom scheme. These values are used when calling AddCustomScheme.
• cef_show_state_t
  Show states supported by CefWindowDelegate::GetInitialShowState.
• cef_ssl_content_status_t
  Supported SSL content status flags. See content/public/common/ssl_status.h for more information.
• cef_ssl_version_t
  Supported SSL version values. See net/ssl/ssl_connection_status_flags.h for more information.
• cef_state_t
  Represents the state of a setting.
• cef_storage_type_t
  Storage types.
• cef_termination_status_t
  Process termination status values.
• cef_test_cert_type_t
  Certificate types supported by CefTestServer::CreateAndStart. The matching certificate file must exist in the “net/data/ssl/certificates” directory. See CefSetDataDirectoryForTests() for related configuration.
• cef_text_field_commands_t
  Represents commands available to TextField.
• cef_text_input_mode_t
  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
• cef_text_style_t
  Text style types. Should be kepy in sync with gfx::TextStyle.
• cef_thread_id_t
  Existing thread IDs.
• cef_thread_priority_t
  Thread priority values listed in increasing order of importance.
• cef_touch_event_type_t
  Touch points states types.
• cef_touch_handle_state_flags_t
  Values indicating what state of the touch handle is set.
• cef_transition_type_t
  Transition type for a request. Made up of one source value and 0 or more qualifiers.
• cef_uri_unescape_rule_t
  URI unescape rules passed to CefURIDecode().
• cef_urlrequest_flags_t
  Flags used to customize the behavior of CefURLRequest.
• cef_urlrequest_status_t
  Flags that represent CefURLRequest status.
• cef_v8_accesscontrol_t
  V8 access control values.
• cef_v8_propertyattribute_t
  V8 property attribute values.
• cef_value_type_t
  Supported value types.
• cef_window_open_disposition_t
  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.
• cef_xml_encoding_type_t
  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.
• cef_xml_node_type_t
  XML node types.

Functions

• cef_basetime_now^⚠
  Retrieve the current system time.
• cef_binary_value_create^⚠
  Creates a new object that is not owned by any other object. The specified |data| will be copied.
• cef_browser_host_create_browser^⚠
  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.
• cef_browser_host_create_browser_sync^⚠
  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.
• cef_browser_view_create^⚠
  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.
• cef_browser_view_get_for_browser^⚠
  Returns the BrowserView associated with |browser|.
• cef_clear_scheme_handler_factories^⚠
  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().
• cef_command_line_create^⚠
  Create a new cef_command_line_t instance.
• cef_command_line_get_global^⚠
  Returns the singleton global cef_command_line_t object. The returned object will be read-only.
• cef_cookie_manager_get_global_manager^⚠
  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().
• cef_create_context_shared^⚠
  Creates a new context object that shares storage with |other| and uses an optional |handler|.
• cef_currently_on^⚠
  Returns true (1) if called on the specified thread. Equivalent to using cef_task_runner_t::GetForThread(threadId)->belongs_to_current_thread().
• cef_dictionary_value_create^⚠
  Creates a new object that is not owned by any other object.
• cef_display_convert_screen_point_from_pixels^⚠
  Convert |point| from pixel screen coordinates to DIP screen coordinates. This function is only used on Windows.
• cef_display_convert_screen_point_to_pixels^⚠
  Convert |point| from DIP screen coordinates to pixel screen coordinates. This function is only used on Windows.
• cef_display_convert_screen_rect_from_pixels^⚠
  Convert |rect| from pixel screen coordinates to DIP screen coordinates. This function is only used on Windows.
• cef_display_convert_screen_rect_to_pixels^⚠
  Convert |rect| from DIP screen coordinates to pixel screen coordinates. This function is only used on Windows.
• cef_display_get_alls^⚠
  Returns all Displays. Mirrored displays are excluded; this function is intended to return distinct, usable displays.
• cef_display_get_count^⚠
  Returns the total number of Displays. Mirrored displays are excluded; this function is intended to return the number of distinct, usable displays.
• cef_display_get_matching_bounds^⚠
  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.
• cef_display_get_nearest_point^⚠
  Returns the Display nearest |point|. Set |input_pixel_coords| to true (1) if |point| is in pixel screen coordinates instead of DIP screen coordinates.
• cef_display_get_primary^⚠
  Returns the primary Display.
• cef_do_message_loop_work^⚠
  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.
• cef_drag_data_create^⚠
  Create a new cef_drag_data_t object.
• cef_execute_process^⚠
  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).
• cef_get_xdisplay^⚠
• cef_image_create^⚠
  Create a new cef_image_t. It will initially be NULL. Use the Add*() functions to add representations at different scale factors.
• cef_initialize^⚠
  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).
• cef_is_cert_status_error^⚠
  Returns true (1) if the certificate status represents an error.
• cef_list_value_create^⚠
  Creates a new object that is not owned by any other object.
• cef_media_router_get_global^⚠
  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().
• cef_menu_model_create^⚠
  Create a new MenuModel with the specified |delegate|.
• cef_panel_create^⚠
  Create a new Panel.
• cef_post_data_create^⚠
  Create a new cef_post_data_t object.
• cef_post_data_element_create^⚠
  Create a new cef_post_data_element_t object.
• cef_post_delayed_task^⚠
  Post a task for delayed execution on the specified thread. Equivalent to using cef_task_runner_t::GetForThread(threadId)->PostDelayedTask(task, delay_ms).
• cef_post_task^⚠
  Post a task for execution on the specified thread. Equivalent to using cef_task_runner_t::GetForThread(threadId)->PostTask(task).
• cef_preference_manager_get_global^⚠
  Returns the global preference manager object.
• cef_print_settings_create^⚠
  Create a new cef_print_settings_t object.
• cef_process_message_create^⚠
  Create a new cef_process_message_t object with the specified name.
• cef_quit_message_loop^⚠
  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.
• cef_register_extension^⚠
  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.
• cef_register_scheme_handler_factory^⚠
  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().
• cef_request_context_create_context^⚠
  Creates a new context object with the specified |settings| and optional |handler|.
• cef_request_context_get_global_context^⚠
  Returns the global context object.
• cef_request_create^⚠
  Create a new cef_request_t object.
• cef_response_create^⚠
  Create a new cef_response_t object.
• cef_run_message_loop^⚠
  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.
• cef_shutdown^⚠
  This function should be called on the main application thread to shut down the CEF browser process before the application exits.
• cef_stream_reader_create_for_data^⚠
  Create a new cef_stream_reader_t object from data.
• cef_stream_reader_create_for_file^⚠
  Create a new cef_stream_reader_t object from a file.
• cef_stream_reader_create_for_handler^⚠
  Create a new cef_stream_reader_t object from a custom handler.
• cef_stream_writer_create_for_file^⚠
  Create a new cef_stream_writer_t object for a file.
• cef_stream_writer_create_for_handler^⚠
  Create a new cef_stream_writer_t object for a custom handler.
• cef_string_ascii_to_utf16^⚠
• cef_string_ascii_to_wide^⚠
  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.
• cef_string_list_alloc^⚠
  Allocate a new string map.
• cef_string_list_append^⚠
  Append a new value at the end of the string list.
• cef_string_list_clear^⚠
  Clear the string list.
• cef_string_list_copy^⚠
  Creates a copy of an existing string list.
• cef_string_list_free^⚠
  Free the string list.
• cef_string_list_size^⚠
  Return the number of elements in the string list.
• cef_string_list_value^⚠
  Retrieve the value at the specified zero-based string list index. Returns true (1) if the value was successfully retrieved.
• cef_string_map_alloc^⚠
  Allocate a new string map.
• cef_string_map_append^⚠
  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.
• cef_string_map_clear^⚠
  Clear the string map.
• cef_string_map_find^⚠
  Return the value assigned to the specified key.
• cef_string_map_free^⚠
  Free the string map.
• cef_string_map_key^⚠
  Return the key at the specified zero-based string map index.
• cef_string_map_size^⚠
  Return the number of elements in the string map.
• cef_string_map_value^⚠
  Return the value at the specified zero-based string map index.
• cef_string_multimap_alloc^⚠
  Allocate a new string multimap.
• cef_string_multimap_append^⚠
  Append a new key/value pair at the end of the string multimap.
• cef_string_multimap_clear^⚠
  Clear the string multimap.
• cef_string_multimap_enumerate^⚠
  Return the value_index-th value with the specified key.
• cef_string_multimap_find_count^⚠
  Return the number of values with the specified key.
• cef_string_multimap_free^⚠
  Free the string multimap.
• cef_string_multimap_key^⚠
  Return the key at the specified zero-based string multimap index.
• cef_string_multimap_size^⚠
  Return the number of elements in the string multimap.
• cef_string_multimap_value^⚠
  Return the value at the specified zero-based string multimap index.
• cef_string_userfree_utf8_alloc^⚠
• cef_string_userfree_utf8_free^⚠
• cef_string_userfree_utf16_alloc^⚠
• cef_string_userfree_utf16_free^⚠
• cef_string_userfree_wide_alloc^⚠
  These functions allocate a new string structure. They must be freed by calling the associated free function.
• cef_string_userfree_wide_free^⚠
  These functions free the string structure allocated by the associated alloc function. Any string contents will first be cleared.
• cef_string_utf8_clear^⚠
• cef_string_utf8_cmp^⚠
• cef_string_utf8_set^⚠
• cef_string_utf8_to_utf16^⚠
• cef_string_utf8_to_wide^⚠
• cef_string_utf16_clear^⚠
• cef_string_utf16_cmp^⚠
• cef_string_utf16_set^⚠
• cef_string_utf16_to_lower^⚠
  These functions convert utf16 string case using the current ICU locale. This may change the length of the string in some cases.
• cef_string_utf16_to_upper^⚠
• cef_string_utf16_to_utf8^⚠
• cef_string_utf16_to_wide^⚠
• cef_string_wide_clear^⚠
  These functions clear string values. The structure itself is not freed.
• cef_string_wide_cmp^⚠
  These functions compare two string values with the same results as strcmp().
• cef_string_wide_set^⚠
  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.
• cef_string_wide_to_utf8^⚠
  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.
• cef_string_wide_to_utf16^⚠
• cef_task_runner_get_for_current_thread^⚠
  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.
• cef_task_runner_get_for_thread^⚠
  Returns the task runner for the specified CEF thread.
• cef_time_delta^⚠
  Retrieve the delta in milliseconds between two time values. Returns true (1) on success and false (0) on failure.
• cef_time_from_basetime^⚠
  Converts cef_basetime_t to cef_time_t. Returns true (1) on success and false (0) on failure.
• cef_time_from_doublet^⚠
• cef_time_from_timet^⚠
• cef_time_now^⚠
  Retrieve the current system time. Returns true (1) on success and false (0) on failure.
• cef_time_to_basetime^⚠
  Converts cef_time_t to cef_basetime_t. Returns true (1) on success and false (0) on failure.
• cef_time_to_doublet^⚠
  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.
• cef_time_to_timet^⚠
  Converts cef_time_t to/from time_t. Returns true (1) on success and false (0) on failure.
• cef_v8context_get_current_context^⚠
  Returns the current (top) context object in the V8 context stack.
• cef_v8context_get_entered_context^⚠
  Returns the entered (bottom) context object in the V8 context stack.
• cef_v8context_in_context^⚠
  Returns true (1) if V8 is currently inside a context.
• cef_v8stack_trace_get_current^⚠
  Returns the stack trace for the currently active context. |frame_limit| is the maximum number of frames that will be captured.
• cef_v8value_create_array^⚠
  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.
• cef_v8value_create_array_buffer^⚠
  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.
• cef_v8value_create_bool^⚠
  Create a new cef_v8value_t object of type bool.
• cef_v8value_create_date^⚠
  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.
• cef_v8value_create_double^⚠
  Create a new cef_v8value_t object of type double.
• cef_v8value_create_function^⚠
  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.
• cef_v8value_create_int^⚠
  Create a new cef_v8value_t object of type int.
• cef_v8value_create_null^⚠
  Create a new cef_v8value_t object of type null.
• cef_v8value_create_object^⚠
  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.
• cef_v8value_create_promise^⚠
  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.
• cef_v8value_create_string^⚠
  Create a new cef_v8value_t object of type string.
• cef_v8value_create_uint^⚠
  Create a new cef_v8value_t object of type unsigned int.
• cef_v8value_create_undefined^⚠
  Create a new cef_v8value_t object of type undefined.
• cef_value_create^⚠
  Creates a new object.
• cef_window_create_top_level^⚠
  Create a new Window.

Type Aliases

• XDisplay
• XEvent
• __time_t
• __uint16_t
• __uint_least16_t
• cef_accessibility_handler_t
  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.
• cef_app_t
  Implement this structure to provide handler implementations. Methods will be called by the process and/or thread indicated.
• cef_audio_handler_t
  Implement this structure to handle audio events.
• cef_audio_parameters_t
  Structure representing the audio parameters for setting up the audio handler.
• cef_auth_callback_t
  Callback structure used for asynchronous continuation of authentication requests.
• cef_base_ref_counted_t
• cef_base_scoped_t
• cef_basetime_t
  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).
• cef_before_download_callback_t
  Callback structure used to asynchronously continue a download.
• cef_binary_value_t
  Structure representing a binary value. Can be used on any process and thread.
• cef_box_layout_settings_t
  Settings used when initializing a CefBoxLayout.
• cef_browser_host_t
  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.
• cef_browser_process_handler_t
  Structure used to implement browser process callbacks. The functions of this structure will be called on the browser process main thread unless otherwise indicated.
• cef_browser_settings_t
  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.
• cef_browser_t
  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.
• cef_browser_view_delegate_t
  Implement this structure to handle BrowserView events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
• cef_browser_view_t
  A View hosting a cef_browser_t instance. Methods must be called on the browser process UI thread unless otherwise indicated.
• cef_callback_t
  Generic callback structure used for asynchronous continuation.
• cef_char_t
• cef_client_t
  Implement this structure to provide handler implementations.
• cef_color_t
• cef_command_handler_t
  Implement this structure to handle events related to commands. The functions of this structure will be called on the UI thread.
• cef_command_line_t
  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.
• cef_completion_callback_t
  Generic callback structure used for asynchronous completion.
• cef_composition_underline_t
  Structure representing IME composition underline information. This is a thin wrapper around Blink’s WebCompositionUnderline class and should be kept in sync with that.
• cef_context_menu_handler_t
  Implement this structure to handle context menu events. The functions of this structure will be called on the UI thread.
• cef_context_menu_params_t
  Provides information about the context menu state. The functions of this structure can only be accessed on browser process the UI thread.
• cef_cookie_access_filter_t
  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.
• cef_cookie_manager_t
  Structure used for managing cookies. The functions of this structure may be called on any thread unless otherwise indicated.
• cef_cookie_t
  Cookie information.
• cef_cookie_visitor_t
  Structure to implement for visiting cookie values. The functions of this structure will always be called on the UI thread.
• cef_cursor_info_t
  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_delete_cookies_callback_t
  Structure to implement to be notified of asynchronous completion via cef_cookie_manager_t::delete_cookies().
• cef_dev_tools_message_observer_t
  Callback structure for cef_browser_host_t::AddDevToolsMessageObserver. The functions of this structure will be called on the browser process UI thread.
• cef_dialog_handler_t
  Implement this structure to handle dialog events. The functions of this structure will be called on the browser process UI thread.
• cef_dictionary_value_t
  Structure representing a dictionary value. Can be used on any process and thread.
• cef_display_handler_t
  Implement this structure to handle events related to browser display state. The functions of this structure will be called on the UI thread.
• cef_display_t
  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.
• cef_domdocument_t
  Structure used to represent a DOM document. The functions of this structure should only be called on the render process main thread thread.
• cef_domnode_t
  Structure used to represent a DOM node. The functions of this structure should only be called on the render process main thread.
• cef_domvisitor_t
  Structure to implement for visiting the DOM. The functions of this structure will be called on the render process main thread.
• cef_download_handler_t
  Structure used to handle file downloads. The functions of this structure will called on the browser process UI thread.
• cef_download_image_callback_t
  Callback structure for cef_browser_host_t::DownloadImage. The functions of this structure will be called on the browser process UI thread.
• cef_download_item_callback_t
  Callback structure used to asynchronously cancel a download.
• cef_download_item_t
  Structure used to represent a download item.
• cef_drag_data_t
  Structure used to represent drag data. The functions of this structure may be called on any thread.
• cef_drag_handler_t
  Implement this structure to handle events related to dragging. The functions of this structure will be called on the UI thread.
• cef_draggable_region_t
  Structure representing a draggable region.
• cef_extension_handler_t
  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.
• cef_extension_t
  Object representing an extension. Methods may be called on any thread unless otherwise indicated.
• cef_file_dialog_callback_t
  Callback structure for asynchronous continuation of file dialog requests.
• cef_find_handler_t
  Implement this structure to handle events related to find results. The functions of this structure will be called on the UI thread.
• cef_focus_handler_t
  Implement this structure to handle events related to focus. The functions of this structure will be called on the UI thread.
• cef_frame_handler_t
  Implement this structure to handle events related to cef_frame_t life span. The order of callbacks is:
• cef_frame_t
  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.
• cef_get_extension_resource_callback_t
  Callback structure used for asynchronous continuation of cef_extension_handler_t::GetExtensionResource.
• cef_image_t
  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.
• cef_insets_t
  Structure representing insets.
• cef_jsdialog_callback_t
  Callback structure used for asynchronous continuation of JavaScript dialog requests.
• cef_jsdialog_handler_t
  Implement this structure to handle events related to JavaScript dialogs. The functions of this structure will be called on the UI thread.
• cef_key_event_t
  Structure representing keyboard event information.
• cef_keyboard_handler_t
  Implement this structure to handle events related to keyboard input. The functions of this structure will be called on the UI thread.
• cef_life_span_handler_t
  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.
• cef_list_value_t
  Structure representing a list value. Can be used on any process and thread.
• cef_load_handler_t
  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).
• cef_main_args_t
  Structure representing CefExecuteProcess arguments.
• cef_media_access_callback_t
  Callback structure used for asynchronous continuation of media access permission requests.
• cef_media_observer_t
  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.
• cef_media_route_create_callback_t
  Callback structure for cef_media_router_t::CreateRoute. The functions of this structure will be called on the browser process UI thread.
• cef_media_route_t
  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.
• cef_media_router_t
  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.
• cef_media_sink_device_info_callback_t
  Callback structure for cef_media_sink_t::GetDeviceInfo. The functions of this structure will be called on the browser process UI thread.
• cef_media_sink_device_info_t
  Device information for a MediaSink object.
• cef_media_sink_t
  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.
• cef_media_source_t
  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.
• cef_menu_model_delegate_t
  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.
• cef_menu_model_t
  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.
• cef_mouse_event_t
  Structure representing mouse event information.
• cef_navigation_entry_t
  Structure used to represent an entry in navigation history.
• cef_navigation_entry_visitor_t
  Callback structure for cef_browser_host_t::GetNavigationEntries. The functions of this structure will be called on the browser process UI thread.
• cef_overlay_controller_t
  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.
• cef_panel_delegate_t
  Implement this structure to handle Panel events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
• cef_panel_t
  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.
• cef_pdf_print_callback_t
  Callback structure for cef_browser_host_t::PrintToPDF. The functions of this structure will be called on the browser process UI thread.
• cef_pdf_print_settings_t
  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
• cef_permission_handler_t
  Implement this structure to handle events related to permission requests. The functions of this structure will be called on the browser process UI thread.
• cef_permission_prompt_callback_t
  Callback structure used for asynchronous continuation of permission prompts.
• cef_point_t
  Structure representing a point.
• cef_popup_features_t
  Popup window features.
• cef_post_data_element_t
  Structure used to represent a single element in the request post data. The functions of this structure may be called on any thread.
• cef_post_data_t
  Structure used to represent post data for a web request. The functions of this structure may be called on any thread.
• cef_preference_manager_t
  Manage access to preferences. Many built-in preferences are registered by Chromium. Custom preferences can be registered in cef_browser_process_handler_t::OnRegisterCustomPreferences.
• cef_preference_registrar_t
  Structure that manages custom preference registrations.
• cef_print_dialog_callback_t
  Callback structure for asynchronous continuation of print dialog requests.
• cef_print_handler_t
  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.
• cef_print_job_callback_t
  Callback structure for asynchronous continuation of print job requests.
• cef_print_settings_t
  Structure representing print settings.
• cef_process_message_t
  Structure representing a message. Can be used on any process and thread.
• cef_range_t
  Structure representing a range.
• cef_read_handler_t
  Structure the client can implement to provide a custom stream reader. The functions of this structure may be called on any thread.
• cef_rect_t
  Structure representing a rectangle.
• cef_registration_t
  Generic callback structure used for managing the lifespan of a registration.
• cef_render_handler_t
  Implement this structure to handle events when window rendering is disabled. The functions of this structure will be called on the UI thread.
• cef_render_process_handler_t
  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.
• cef_request_context_settings_t
  Request context initialization settings. Specify NULL or 0 to get the recommended default values.
• cef_request_context_t
  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.
• cef_request_handler_t
  Implement this structure to handle events related to browser requests. The functions of this structure will be called on the thread indicated.
• cef_request_t
  Structure used to represent a web request. The functions of this structure may be called on any thread.
• cef_resolve_callback_t
  Callback structure for cef_request_context_t::ResolveHost.
• cef_resource_bundle_handler_t
  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.
• cef_resource_handler_t
  Structure used to implement a custom request handler structure. The functions of this structure will be called on the IO thread unless otherwise indicated.
• cef_resource_read_callback_t
  Callback for asynchronous continuation of cef_resource_handler_t::read().
• cef_resource_request_handler_t
  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.
• cef_resource_skip_callback_t
  Callback for asynchronous continuation of cef_resource_handler_t::skip().
• cef_response_filter_t
  Implement this structure to filter resource response content. The functions of this structure will be called on the browser process IO thread.
• cef_response_t
  Structure used to represent a web response. The functions of this structure may be called on any thread.
• cef_run_context_menu_callback_t
  Callback structure used for continuation of custom context menu display.
• cef_run_file_dialog_callback_t
  Callback structure for cef_browser_host_t::RunFileDialog. The functions of this structure will be called on the browser process UI thread.
• cef_run_quick_menu_callback_t
  Callback structure used for continuation of custom quick menu display.
• cef_scheme_handler_factory_t
  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.
• cef_scheme_registrar_t
  Structure that manages custom scheme registrations.
• cef_screen_info_t
  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.
• cef_select_client_certificate_callback_t
  Callback structure used to select a client certificate for authentication.
• cef_set_cookie_callback_t
  Structure to implement to be notified of asynchronous completion via cef_cookie_manager_t::set_cookie().
• cef_settings_t
  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_shared_memory_region_t
  Structure that wraps platform-dependent share memory region mapping.
• cef_size_t
  Structure representing a size.
• cef_sslinfo_t
  Structure representing SSL information.
• cef_sslstatus_t
  Structure representing the SSL information for a navigation entry.
• cef_stream_reader_t
  Structure used to read data from a stream. The functions of this structure may be called on any thread.
• cef_stream_writer_t
  Structure used to write data to a stream. The functions of this structure may be called on any thread.
• cef_string_list_t
  CEF string maps are a set of key/value string pairs.
• cef_string_map_t
  CEF string maps are a set of key/value string pairs.
• cef_string_multimap_t
  CEF string multimaps are a set of key/value string pairs. More than one value can be assigned to a single key.
• cef_string_t
• cef_string_userfree_t
• cef_string_userfree_utf8_t
• cef_string_userfree_utf16_t
• cef_string_userfree_wide_t
  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_utf8_t
• cef_string_utf16_t
• cef_string_visitor_t
  Implement this structure to receive string values asynchronously.
• cef_string_wide_t
  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.
• cef_task_runner_t
  Structure that asynchronously executes tasks on the associated thread. It is safe to call the functions of this structure on any thread.
• cef_task_t
  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.
• cef_time_t
  Time information. Values should always be in UTC.
• cef_touch_event_t
  Structure representing touch event information.
• cef_touch_handle_state_t
• cef_urlparts_t
  URL component parts.
• cef_v8accessor_t
  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.
• cef_v8array_buffer_release_callback_t
  Callback structure that is passed to cef_v8value_t::CreateArrayBuffer.
• cef_v8context_t
  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.
• cef_v8exception_t
  Structure representing a V8 exception. The functions of this structure may be called on any render process thread.
• cef_v8handler_t
  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.
• cef_v8interceptor_t
  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.
• cef_v8stack_frame_t
  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.
• cef_v8stack_trace_t
  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.
• cef_v8value_t
  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.
• cef_value_t
  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.
• cef_view_delegate_t
  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.
• cef_view_t
  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.
• cef_window_delegate_t
  Implement this structure to handle window events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
• cef_window_info_t
  Class representing window information.
• cef_window_t
  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.
• cef_write_handler_t
  Structure the client can implement to provide a custom stream writer. The functions of this structure may be called on any thread.
• cef_x509cert_principal_t
  Structure representing the issuer or subject field of an X.509 certificate.
• cef_x509certificate_t
  Structure representing a X.509 certificate.
• char16_t
• time_t
• wchar_t