1.5 KiB
Additional engine verification
Firefox and WebKit24actual cases passed:6synthetic scenes ×2viewports ×2engines, exact engine versions in JSON. All retain one h1, no document overflow, reduced-motion opacity1 and no browser errors. Mixed attention/clear/focus/pause/resume and phone native rail Enter pass; long escaped diagnostics open through focused Enter. This focused functional run does not add another visual polish pass.
The first WebKit automatic click timed out despite the visible checkbox having a nonzero bounding box. A native coordinate click on that actual box changed7cards to5and updated the summary. Inspection of the installed Playwright injectedScriptSource.js confirmed its WebKit visibility workaround returns false for descendants of closed details regardless of the Theme ::details-content override. The fixture now uses measured native pointer input for WebKit clicks; it does not set open or mutate product state through scripts. Subsequent focus/keyboard and resulting application state are asserted. Retained initial failure is a harness discrepancy, not evidence that the product checkbox was unclickable. Firefox retains normal locator clicks. Official coordinate-input documentation describes bounding_box plus mouse.click.
No human VoiceOver/NVDA listening session is claimed. Existing Chromium AX role/name/state evidence remains distinct from these runtime checks.