Checkpoint web parity through Chromium input tasks
Some checks failed
M6 deployable RC / quick (push) Has been cancelled
M6 deployable RC / chromium (push) Has been cancelled
M6 deployable RC / release (push) Has been cancelled

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

26
docs/status/M14-04C.md Normal file
View File

@@ -0,0 +1,26 @@
# M14-04C Status
status: done
task: Chromium mouse/touch/pen pointer identity and cancellation contract
updated: 2026-08-19 America/New_York
enablingTask: false
parityStateChange: false
## Scope
The main-thread and Offscreen viewport paths now record a shared pointer observation for mouse,
touch, and pen input. Pointer identity, pressure, tilt, button/buttons and `pointercancel` are
preserved with bounded values; unknown pointer types and invalid IDs fail closed. Chromium production
events verified down/cancel pairs for all three pointer types. Firefox/WebKit are excluded.
## Evidence
- `npm --prefix web run build` passed.
- `npm --prefix web run test:chromium-pointer-contract` passed: 2 protocol tests and real Chromium
mouse/touch/pen down/cancel events.
- Checker output: `chromium-pointer-ok types=mouse,touch,pen cancel=PASS execution=DISABLED next=M14-04D`.
- `npm --prefix web run typecheck` and `git diff --check` passed.
## Next Task
`M14-04D`: Chromium IME composition guard for incomplete operators.