Phone hit: viewer headers and UIA stages (group 9) #135
Loading…
Reference in a new issue
No description provided.
Delete branch "void/phone-hit-viewers"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Group 9 of the IconButton phone-hit audit: viewers and UIA stages. Nothing drawn changes.
Changed (7 files, 9 buttons)
Chip as="div"(step counter), not tappableBack/close buttons in a header are single-row, no tappable horizontal neighbour, so plain PhoneHit (no vertical stacks in this group).
Skipped: UrlPreviewCard (2 scroll arrows, 30 px)
The audit proposed PhoneHit. That is wrong:
UrlPreviewHolderBtnisposition: absolute(left/right 0, translateX +-25%), and PhoneHit setsposition: relativeon phones. Which wins depends on stylesheet order, and if PhoneHit wins the arrows drop into the flow and the layout changes. Not applied. Needs a variant that keeps the position (or a hit-area-only class) in PhoneHit.css.ts, which this PR may not touch. Clipping check: the arrows' containing block is the outer relative Box, not the Scroll, so the Scroll does not clip the ::after; the translate puts the drawn button 7.5 px past the holder edge and the 44 px hit area ~14 px past, so whether an ancestor (message/timeline container) clips it is unmeasured.Not measured on a real phone
All of it: hit areas are checked by class and drawn size only (test kit), not by tapping on the Starfire phone run. In the viewer headers the zoom Spread24 adds 10 px margin each side on phones, so the header row grows; not looked at on a 390 px width.
Test
src/app/phoneHit.viewers.test.ts: variant per IconButton in source order plus size tie, no allow-list entries. Mutants (swap in source, test dies): ImageViewer zoom Spread24 -> PhoneHit; SSOStage PhoneHit -> Spread24 (both checks die); PdfViewer Spread24 -> Spread28 (both die); UIAFlowOverlay variant removed.🤖 Generated with Claude Code