tauri-runtime-servocat 1.5.0

Servo-replacement runtime for Tauri: wires html-cat, css-cat, dom-cat, layout-cat, paint-cat, net-cat, boa-cat, ecma-runtime-cat, and web-api-cat into a single rendering + scripting pipeline. v1.5.0 plumbs `PendingWebview::ipc_handler` so a Tauri app's `tauri::Builder::invoke_handler` is stored alongside the webview and can be fired through the inherent `ServocatWebviewDispatch::send_ipc(request)` method (the Rust-side half of the JS<->host IPC bridge). This closes the committed 1.x roadmap; subsequent 1.x patch releases will wire the JS-side `__TAURI_INTERNALS__.postMessage` bridge through to the same handler. The Servo no-AI policy disqualifies upstream contribution; this is the AI-built parallel.

Builds

tauri-runtime-servocat's sandbox limits

All the builds on docs.rs are executed inside a sandbox with limited resources. The limits for this crate are the following:

Available RAM 6.44 GB
Maximum rustdoc execution time 15m
Maximum size of a build log 102.4 kB
Network access blocked
Maximum number of build targets 10

If a build fails because it hit one of those limits please open an issue to get them increased.