fix(anatomy): V1-2.2 the visible wins on the editor canvas

Owner decision 2026-11-01. The canvas paints and hits every point hitbox,
then every zone and trigger, then every visible twin, which captures on
what it paints; a junction's disc is no longer taken by the zone drawn
after it. The PDF view keeps the document order and its bytes. Click
spec: the five fixme run unmarked, six projects incl. a 320 px phone.
This commit is contained in:
bchanot committed 2026-11-01 00:56:11 +01:00
1 parent e67715025c
commit 9c606aa567
13 files changed
+504 -64

No files matched your search

+11 -4
View File
@@ -113,10 +113,17 @@ suite needs Docker in the runner for the sandbox.
## 6. Limits
- Chromium only, but `e2e/ui/canvas-clicks.spec.ts` (V1-2.2: projects
`firefox-desktop`, `webkit-desktop`, `webkit-375`, added when
`playwright install firefox webkit` has put the pinned engines in the cache;
a missing one is named in the run's output and its projects do not run;
harness `e2e/harness/canvas.{html,tsx}`, dev server only). Firefox, WebKit
`chromium-320` (320 × 568, touch, the smallest preview the markers' visible
size is measured on), `firefox-desktop`, `webkit-desktop`, `webkit-375`, the
last three added when `playwright install firefox webkit` has put the pinned
engines in the cache; a missing one is named in the run's output and its
projects do not run; harness `e2e/harness/canvas.{html,tsx}`, dev server
only). WebKit snaps a real tap or click to whole CSS pixels (measured
2026-11-01: a tap at x 100.1 lands right of an edge at 100.4, a click at
100.9 left of it; Chromium keeps the fraction on a click, rounds a tap), so a
real press keeps 1.5 px of margin from any edge it tests; below that margin
the spec asks the browser's own hit test (`elementFromPoint`) at the exact
point. Firefox, WebKit
and the 412 × 915 viewport join every suite at V1-5
(contract §12.5). WebKit's system libraries may need `sudo` (owner action).
Desktop WebKit is not iOS Safari: the owner's manual check on a real iPhone