Crate vs_engine_webkit 

WebKit engine binding for vibesurfer.

This crate hosts the Engine trait — the daemon’s view of “a browser” — and the EngineRuntime that pins the implementation to a dedicated OS thread (the only thread that may call WebKit on either supported platform).

Backends

• [backend::webkit] (macOS) — system WebKit framework via objc2 + objc2-web-kit, driven from the Cocoa main thread.
• backend::wpe (Linux) — WebKitGTK 6 via webkit6 + glib, driven from a thread that owns a GLib main context.
• [backend::webview2] (Windows) — WebView2 via webview2-com + windows-rs, driven from a thread that owns a Win32 message pump.

All backends implement Engine; EngineRuntime::spawn is generic over the constructor so the daemon can pick a backend at runtime without compile-time coupling.

Re-exports

pub use engine::ActTarget;

pub use engine::Action;

pub use engine::AuthBlob;

pub use engine::CaptureScope;

pub use engine::Engine;

pub use engine::EngineCapabilities;

pub use engine::EngineError;

pub use engine::EngineResult;

pub use engine::LayoutBox;

pub use engine::PageHandle;

pub use engine::Viewport;

pub use engine::WaitCondition;

pub use inspector::ConsoleEntry;

pub use inspector::ConsoleLevel;

pub use inspector::Header;

pub use inspector::NetworkEntry;

pub use inspector::NetworkStatus;

pub use inspector::RequestDetail;

pub use inspector::RingBuffer;

pub use runtime::EngineRuntime;

Modules

backend

Concrete Engine implementations.

engine

The Engine trait — the daemon’s view of “a browser”.

inspector

Inspector capture types — ConsoleEntry, NetworkEntry, ring buffer + level/status enums.

runtime

Engine thread + channel bridge.

Functions

version

Returns the crate version (matches the workspace version).