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
Parent systemWebScene
StatusPreview
Modules2
RepositoryWebScene/WebScene.NativeEngine.Probe

The native engine owns script, document state, layout, and paint together so high-frequency component work does not bounce through the managed UI thread.

  1. 01

    Dedicated V8 isolates

  2. 02

    DOM, CSS, layout, Canvas, and SVG

  3. 03

    Immutable native scene publication

  4. 04

    Deterministic compatibility runner

From intent
to working system.

01

Script

V8 executes trusted packaged JavaScript and TypeScript output in a dedicated isolate.

02

Platform

The bounded DOM, CSS, events, layout, Canvas, and SVG surface implements the supported profile.

03

Scene

Native layout and paint produce immutable updates instead of chatty object-level interop.

04

Validate

Curated WPT cases and product-scale fixtures measure declared compatibility.

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.

01 · Install
Terminal
git clone --recurse-submodules https://github.com/wieslawsoltes/WebScene.git
dotnet run --project samples/NativeRuntimeShowcase.Avalonia
02 · Use · javascript
quick-start.js
const canvas = document.querySelector("canvas");
const context = canvas.getContext("2d");
context.fillStyle = "#8ea2ff";
context.fillRect(24, 24, 160, 80);

Use one layer.
Compose the rest.

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.

WebScene

Search everything.

Loading the index…

move open esc close

Preparing metadata and full-text search…