Symptom
e2e/mobile-ios/landing.spec.ts:15 (iPhone SE project, 320px viewport): window.scrollX moves from 0 to 18 after scrollBy({left: 100}) — page is horizontally scrollable, the user-facing overflow guard is broken.
Currently test.fixme(testInfo.project.name === 'iPhone SE', ...) (commit 6507f4b PR #147 unblock).
iPhone 14 + iPhone 15 Pro Max keep their strict assertion (no overflow detected on these viewports).
Hypotheses
- Tailwind purge regression (recent PR-3c-4 hero waterfall layout changes?)
- Flex container conflict on landing hero
overflow-x-clip on html/body utility no longer honored on 320px viewport specifically
Investigation steps
- Bisect commits since fixme was applied (2026-05-08+) on iPhone SE viewport
- Inspect
document.body.scrollWidth vs clientWidth on iPhone SE — find which element overflows
- Check Tailwind safelist for
overflow-x-clip
Reference
- Test fixme commit: 6507f4b
- DoD §C6: docs/prs/PR-D4-PHASE2-A-report.md
Defer to
PR-D5 mobile fixes pass.
Symptom
e2e/mobile-ios/landing.spec.ts:15(iPhone SEproject, 320px viewport):window.scrollXmoves from 0 to 18 afterscrollBy({left: 100})— page is horizontally scrollable, the user-facing overflow guard is broken.Currently
test.fixme(testInfo.project.name === 'iPhone SE', ...)(commit 6507f4b PR #147 unblock).iPhone 14 + iPhone 15 Pro Max keep their strict assertion (no overflow detected on these viewports).
Hypotheses
overflow-x-clipon html/body utility no longer honored on 320px viewport specificallyInvestigation steps
document.body.scrollWidthvsclientWidthon iPhone SE — find which element overflowsoverflow-x-clipReference
Defer to
PR-D5 mobile fixes pass.