chore(memory): V1-2.2 interior rule evidence, tools, LRN-105..107

This commit is contained in:
bchanot committed 2026-11-01 13:40:57 +01:00
1 parent c73415abef
commit e190dfc794
8 files changed
+233

No files matched your search

+21
View File
@@ -723,3 +723,24 @@ Supersedes [[LRN-100]].
**Context**: V1-2.2 canvas click proofs (Playwright, `e2e/harness/canvas.tsx`), 2026-10-30.
**Application**: recompute target box right before each press (`centreOf` per click), or keep layout fixed (output with fixed height, `overflow:hidden`). Treat "first click right, next ones wrong" as layout shift first, hit-test second.
## LRN-105 — WebKit snaps real taps and clicks to whole CSS px: press with 1.5 px margin, else elementFromPoint (2026-11-01)
**Pattern**: WebKit snaps real input to whole CSS px. Playwright `touchscreen.tap` and `mouse.click` at fractional coords land on rounded pixel; hit test then answers rounded point. Chromium keeps fraction on click, rounds tap.
**Context**: V1-2.2 canvas click proofs, WebKit 27.2 (Playwright 1.64.1), desktop 1280 and iPhone SE 375 emulation, 2026-11-01. Measured: tap at x 100.1 lands right of edge at 100.4; click at 100.9 lands left of it. Two junction-edge tests failed only on WebKit until margin added.
**Application**: real presses keep ≥ 1.5 px margin from any edge they test. Below that margin ask `document.elementFromPoint` at exact point instead of pressing. Never read a WebKit-only edge miss as hit-test bug before checking snapping.
## LRN-106 — Firefox getBoundingClientRect drifts (1/60 px units, stroke included); confirm by painted pixels (2026-11-01)
**Pattern**: Firefox `getBoundingClientRect` drifts from rendered geometry: client rects in 1/60 px app units, and include stroke of element. Rendering itself exact. Size checks via client rects in Firefox show error up to 0.4 % (24 % on 0.067 px hitbox) though pixels are right.
**Context**: V1-2.2 frame and visible-size probes vs Rust f64 expectation, Firefox 157 (Playwright 1.64.1), preview box 286 × 310, 2026-11-01. Chromium 156 / WebKit 27.2 agree with core ≤ 8.2e-5 relative on same cases. One-unit frame: Firefox rects 3.3 % off 286 px/unit while painted pixels exact.
**Application**: compare geometry across engines with stroke none on probed element, and confirm Firefox outliers by painted pixels (canvas/screenshot count) before calling a rendering gap. Report Firefox rect gap as measurement artifact, not defect.
## LRN-107 — WebKit and Chromium stop painting SVG at tiny viewBox spans (f32): floors from painted pixels (2026-11-01)
**Pattern**: WebKit and Chromium stop painting SVG at tiny viewBox spans. Frame span 2⁻⁷ → WebKit paints nothing; Chromium drifts at 2⁻¹⁴ (0.46 px), paints nothing at 2⁻²⁰; Firefox exact at every span. f32 view transform the cause.
**Context**: V1-2.2 frame range rules, disc a quarter of frame in 286 px box, painted-pixel count, WebKit 27.2 / Chromium 156 / Firefox 157 (Playwright 1.64.1), 2026-11-01. First span floor 2⁻²⁰ withdrawn on this measure; floor set to 1 unit (factor 32 from WebKit's last exact span 2⁻⁵).
**Application**: bound SVG frame spans and offsets by browser f32 range before trusting geometry; derive floors from painted pixels in all three engines, never from f64 math alone.