Files
gex/test/core/pointerlock-compositor.test.js
velzieandClaude Opus 5.5 e3f8c9e9f7 runtime: CompositorWindows and MesaGl in the single-thread build
The scene compositor runs in the system Worker, beside the memories it
reads (compositor-in-realm.js, one module for the System and the old
path); the page's CompositorWindows says before boot what the Worker must
make and relays its canvas's messages there (`comp`, `comp-out`). The
non-pthread Mesa (gex/st/) runs in that compositor, started by MesaGl's
start() or a program's first GL call (`gl-wanted`), each process's submit
on its own memory.

wl-bridge.mjs asks whether a buffer is shared without naming
SharedArrayBuffer where the page has none: the compositor's frame loop
died of a ReferenceError and drew once.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_381c5a280a87404da0f8d9994180b091
2026-11-02 12:35:16 -05:00

8 lines
347 B
JavaScript

// PointerLock through the scene compositor (pointerlock.test.js).
import { pointerLock } from './pointerlock.test.js';
export const meta = { hosts: ['browser'], images: ['busybox'], timeout: 120, html: `<style>html, body { margin: 0; }</style>
<canvas id="out" width="800" height="600"></canvas>` };
export default (t) => pointerLock(t, true);