Core APIs

Category description: Foundational interfaces: process bootstrap, browser lifecycle, frames, DOM, requests, and data objects.

Pages in this category

Page	Source Header
CefApiHash	cef_api_hash.h
CefApp	cef_app.h
CefBaseScoped	cef_base.h
CefBrowser	cef_browser.h
CefBrowserProcessHandler	cef_browser_process_handler.h
CefClient	cef_client.h
CefCommandLine	cef_command_line.h
CefDOMNode	cef_dom.h
CefDownloadItem	cef_download_item.h
CefDragData	cef_drag_data.h
CefFrame	cef_frame.h
CefImage	cef_image.h
CefMenuModel	cef_menu_model.h
CefNavigationEntry	cef_navigation_entry.h
CefPrintSettings	cef_print_settings.h
CefRenderProcessHandler	cef_render_process_handler.h
CefRequest	cef_request.h
CefRequestContext	cef_request_context.h
CefResourceBundle	cef_resource_bundle.h
CefResponse	cef_response.h
CefSSLInfo	cef_ssl_info.h
CefVersionInfo	cef_version_info.h
CefX509Certificate	cef_x509_certificate.h

How to use these pages

Each page is a single standalone markdown file documenting one CEF header. The page begins with the header name and an overview, then has one ## section per interface declared in that header. Each interface section lists:

• Source File — the CEF header path
• Process / Thread Context — verbatim from the header comment
• Purpose — one or two sentences from the header comment
• Methods — every public method with Parameters, Return Value, Usage Instruction, and Threading Constraint
• Usage Example — a cpp code block grounded in the actual API signatures

Where the source header does not specify a threading constraint, the page explicitly says "Threading constraint not specified in source." — these docs never guess.

See Also

• Back to v151 documentation
• Contributing guide