fix(anatomy): V1-2.2 refuse zones without a usable interior
A polygon or path zone or trigger must fill a disc of 4 CSS px on the 320 x 568 preview under the layer's nonzero rule, stroke left out: conservative widest-disc search on the flattened outline, caps and a per-sheet budget, closed codes interior_too_small and marker_interior_too_small. Browser probe on six projects.
This commit is contained in:
1 parent
de2dfb392e
commit
8dd2d78d38
18 files changed
+1852
-38
No files matched your search
@@ -123,7 +123,16 @@ suite needs Docker in the runner for the sandbox.
|
||||
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
|
||||
point. `e2e/ui/interior-clicks.spec.ts` runs on the same six projects
|
||||
(V1-2.2, the interior rule): the core's probe cases
|
||||
(`e2e/fixtures/interior-probe.json`, generated and drift-checked by
|
||||
`crates/core/tests/interior_probe.rs`, `MAKE_INTERIOR_PROBE=1` rewrites it) in
|
||||
the phone preview's 286 × 310 box (harness `e2e/harness/interior.{html,ts}`,
|
||||
dev server only), then the equine zones in the canvas harness. Chromium's touch
|
||||
adjustment gives a point the taps up to about 10 px around its disc
|
||||
(measured 2026-11-01, `chromium-320` and `chromium-375`; WebKit 375 does
|
||||
not), so the real press on an equine zone goes where its fill lies farthest
|
||||
from every disc. 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
|
||||
|
||||
Reference in new issue
Block a user