route-graphics 1.47.0 → 1.48.0

package/README.md

@@ -80,6 +80,27 @@ other backend. The selected value is available as `app.rendererType`. Inline
 shader effects always provide both GLSL and WGSL so the same state works on
 either backend.
 
+For scene/editor/preview handoffs, use `await app.reset({ eventHandler })`
+instead of destroying and recreating the renderer. Reset clears the display tree,
+animations, audio playback, keyboard bindings, DOM input controls, cursor state,
+snapshot audio-effect requests, and pending render callbacks while preserving the
+same canvas and GPU context. A render that reset interrupts is reported to the
+previous `eventHandler` as `renderComplete` with `aborted: true`, and the first
+render after a reset calls `onFirstRender` again.
+It accepts runtime initialization overrides, including width/height and plugins;
+renderer backend, fallback policy, and debug mode must remain unchanged.
+Loaded assets stay owned by the instance: use `unloadAssets()` for media no longer
+needed, and `destroy()` when the rendering surface is permanently discarded.
+Serialize reset with asset loading and unloading. This avoids repeated WebGL
+context creation during rapid view changes, which can exhaust WebKit's context
+accounting even after explicit context loss ([WebKit bug 218305](https://bugs.webkit.org/show_bug.cgi?id=218305)).
+
+Run `bun run build && node scripts/testRendererReset.mjs` to verify 40 resets in
+Chromium and WebKit reuse one context, clear runtime state, and release the context
+on final destruction, and that reset removes input controls and keyboard
+bindings, stops animations, and keeps pointer events working. CI runs it in the
+browser suite; the `reset-stops-audio` AVT spec covers audio.
+
 `createAssetBufferManager()` may keep image and video assets as direct source
 URLs when possible, while audio and font assets remain buffer-backed.