Checkpoint web parity through Chromium input tasks
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

This commit is contained in:
mes123456
2026-08-19 10:39:03 -04:00
parent 5a11045ca5
commit 380cbed4ff
634 changed files with 41862 additions and 212 deletions

21
docs/status/M14-01C.md Normal file
View File

@@ -0,0 +1,21 @@
# M14-01C Status
status: done
task: WebKit capability probe
updated: 2026-08-19 America/New_York
enablingTask: false
parityStateChange: false
WebKit `26.5` was probed against the rebuilt production assets with COOP/COEP isolation. WASM, Worker,
IndexedDB, WebGL2, OffscreenCanvas and isolation passed. OPFS and WebGPU are explicitly blocked; the
result does not change the Chromium-only release claim.
## Evidence
- `npm --prefix web run test:webkit-capability` passed.
- Checker output: `webkit-capability-ok version=26.5 wasm=PASS,worker=PASS,opfs=BLOCKED,indexedDB=PASS,webgl2=PASS,webgpu=BLOCKED,offscreen=PASS,isolation=PASS execution=DISABLED next=M14-01D`.
- `git diff --check` passed.
## Next Task
`M14-01D`: probe identity and GPU/OS adapter recording.