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

View File

@@ -6,7 +6,10 @@ storage, and desktop/WASM round-trip tests.
The current browser baseline is Chromium only. The release browser suite covers
both the main-thread WebGL renderer and the OffscreenCanvas Worker renderer.
Firefox and WebKit are intentionally outside the current test and release scope.
Firefox and WebKit are permanently outside this project's test, CI, evidence, and release scope.
The iron rule is Chromium-only browser execution: never launch, probe, or claim support from
Firefox or WebKit. Historical Firefox/WebKit reports are archival context only and are not normative
support evidence.
## Layout
@@ -29,7 +32,7 @@ npm --prefix web run build
npm --prefix web run test:browser
```
See `docs/CURRENT_EXECUTION_PLAN.md` for the current task order,
See `docs/EXECUTION_QUEUE.md` for the current task order and `docs/README.md` for the document map,
`docs/PROJECT_STATUS_AND_NEXT_WORK.md` for the implemented scope, and
`docs/BLENDER_5_2_FULL_WEB_PARITY_EXECUTION_PLAN.md` for the normative M12-M23
full-parity execution plan. The domain overview and coverage cross-check are in