V8, DOM, CSS, layout, Canvas, and SVG
Native Scene Runtime
Keep web-authored hot paths native and publish a compact scene to the host.
Explore source ↗Capability
The native engine owns script, document state, layout, and paint together so high-frequency component work does not bounce through the managed UI thread.
- 01
Dedicated V8 isolates
- 02
DOM, CSS, layout, Canvas, and SVG
- 03
Immutable native scene publication
- 04
Deterministic compatibility runner
How it composes
From intent
to working system.
Script
V8 executes trusted packaged JavaScript and TypeScript output in a dedicated isolate.
Platform
The bounded DOM, CSS, events, layout, Canvas, and SVG surface implements the supported profile.
Scene
Native layout and paint produce immutable updates instead of chatty object-level interop.
Validate
Curated WPT cases and product-scale fixtures measure declared compatibility.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
git clone --recurse-submodules https://github.com/wieslawsoltes/WebScene.gitdotnet run --project samples/NativeRuntimeShowcase.Avaloniaconst canvas = document.querySelector("canvas");const context = canvas.getContext("2d");context.fillStyle = "#8ea2ff";context.fillRect(24, 24, 160, 80);Modules in this capability
Use one layer.
Compose the rest.
Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.