Files
Chris Tate 8fc933b9db fix(windows): accelerate gpu surface presentation (#258)
* fix(windows): accelerate gpu surface presentation

- Render retained binary canvas packets through Direct2D and DirectWrite.
- Preserve dirty-region updates and GPU effects with a safe software fallback.
- Wire and validate the renderer across supported Windows build paths.

Co-authored-by: Omer Shatzberg <131801941+oshtz@users.noreply.github.com>

* fix(windows): harden Direct2D presentation

* fix(sdk): separate GPU backend request types

* fix(windows): honor GPU surface fallback contracts

* fix(windows): scale transformed blur kernels

* fix: harden Windows GPU surface presentation

* fix(windows): harden gpu blur and caption sampling

* fix(runtime): bypass packets for software surfaces

* fix(windows): preserve precise gpu surface updates

* fix(windows): reconcile GPU presenter state

* fix: preserve retained canvas resources

* fix: preserve Windows canvas packet fidelity

---------

Co-authored-by: Omer Shatzberg <131801941+oshtz@users.noreply.github.com>
2026-08-02 15:59:44 -05:00
..
2026-06-25 10:53:58 -05:00

Browser Example

A no-build vanilla HTML/CSS/JS example that uses the layered WebViews API for isolated page content.

Run it from this directory:

zig build run

Or from the repository root:

zig build run-browser

The root command uses this example's system-WebView default unless you explicitly pass -Dweb-engine=chromium.

The frontend lives in frontend/ and is served directly as zero://app/index.html.

The page content runs in an isolated child WebView. Page WebViews do not receive window.zero; all navigation and sizing is controlled by the browser chrome through the handle returned by window.zero.webviews.create().

This example allows all navigation origins so it can browse arbitrary pages. Treat that as demo-only policy, not a production template. The chrome page keeps a strict CSP; arbitrary page navigation is controlled by the native navigation policy. Chromium/CEF builds are currently macOS-only; use the system WebView backend on Linux and Windows for this example. main WebView layering is best effort and may be ignored by a backend. Windows WebView support is still in progress and does not yet support the main WebView resizing this example uses.