Files
workinf_Blender_Wasm/docs/status/M14-01E.md
mes123456 380cbed4ff
Some checks are pending
M6 deployable RC / quick (push) Waiting to run
M6 deployable RC / chromium (push) Blocked by required conditions
M6 deployable RC / release (push) Blocked by required conditions
Checkpoint web parity through Chromium input tasks
2026-08-19 10:39:03 -04:00

30 lines
959 B
Markdown

# M14-01E Status
status: done
task: Chromium WebGPU fail-closed boundary
updated: 2026-08-19 America/New_York
enablingTask: false
parityStateChange: false
## Scope
Chromium routing was checked against the production render protocol. A bounded Eevee request using
WebGPU returns `BLOCKED/WEBGPU_RENDERER_UNAVAILABLE` when no bundled adapter is available, while the
same bounded request using WebGL2 remains `READY/WEB_LOCAL_BOUNDED`. This task does not launch Firefox
or WebKit.
## Evidence
- `npm --prefix web run test:chromium-webgpu-boundary` passed.
- Checker output: `chromium-webgpu-boundary-ok webgpu=BLOCKED/WEBGPU_RENDERER_UNAVAILABLE webgl2=READY execution=DISABLED next=M14-04A`.
- `git diff --check` passed.
## Next Task
`M14-04A`: Chromium GPU/memory budget device tier selection.
## Rollback
Remove the Chromium boundary checker, report, manifest, package command and this status/task entry;
restore `M14-01D` as the queue tail.