Read-only navigation state for one exact native CEF browser lifetime. The CEF UI thread
advances it before input submission can be admitted on that same thread.
No lock is held while calling CEF or awaiting a renderer response.
Opaque process-local proof of an observed native browser/document lifetime.
Compare it with WebviewSnapshot::document in the final UI-thread callback
before an effect. A token alone does not authorize an account or profile.
Windowless browser configuration. The application owns painting, input/IME
forwarding and composition; Tauri keeps its IPC, protocols and browser lifecycle.
Offscreen webviews use Alloy style and cannot be reparented.
Native state sampled on the CEF UI thread immediately before a
with_webview callback. This does not assert renderer responsiveness or
that the view is unobscured on screen.
What to do with the profile on disk when a newer Chromium milestone than the one this
binary embeds last used it: the application was rolled back to a release on an older
CEF.
Native events for application rendering and input forwarding, on the event-loop thread.
Destroyed is delivered before the runtime releases the window, including on exit.
Marks the application entry point so non-browser CEF processes (renderer, GPU, …) are handled.
Mark a function as the CEF entry point. It creates a main function that only runs
the provided function for the browser process, and runs the CEF helper process
for other processes (renderer, GPU, plugin, etc.).