From 6bcb271bfbac2a16e006b2a324f6f73e344506c9 Mon Sep 17 00:00:00 2001 From: Brad Stricherz Date: Sat, 7 Nov 2026 16:59:11 -0600 Subject: [PATCH 01/14] docs: plan for issue 5 Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01AELE7jB1i3uqqrHu3SjJjf --- ...6-11-07-issue-5-layout-breaks-on-mobile.md | 68 +++++++++++++++++++ 1 file changed, 68 insertions(+) create mode 100644 docs/plans/2026-11-07-issue-5-layout-breaks-on-mobile.md diff --git a/docs/plans/2026-11-07-issue-5-layout-breaks-on-mobile.md b/docs/plans/2026-11-07-issue-5-layout-breaks-on-mobile.md new file mode 100644 index 0000000..5b2efd2 --- /dev/null +++ b/docs/plans/2026-11-07-issue-5-layout-breaks-on-mobile.md @@ -0,0 +1,68 @@ +# Plan: Layout breaks on mobile: header text overlaps and panels overflow at 375px (issue #5) + +Risk tier: Medium. Responsive layout and a new collapse toggle are stateful UI that jsdom cannot lay out, so the layout is proven only by a live browser drive. It alters existing behavior (header, layer panel, popup, GPU panel) across several files, but touches no API, store contract, data, or security code. + +Domain skills: +- superpowers:test-driven-development: invoke. +- chrome-devtools-mcp:a11y-debugging: invoke for the live drive (toggle name, aria-expanded, focus ring, Tab order). +- frontend-design: not applicable because the user fixed the visual direction: keep the existing dark HUD look, only adapt it to narrow screens. +- vercel-react-best-practices: not applicable because there is no data fetching or render performance work; one small `useSyncExternalStore` media query hook. +- dataviz, django, fastapi, expo, payments, email: not applicable because none of that is touched. + +## Acceptance criteria + +1. At 375x812, 768x1024, and 1440x900, no text overlaps: the bounding boxes of the visible header elements (`.classification-badge`, `.header-status`, `.app-title`, `.coord-display`, `.time-display`, and visible `.header-sep`) do not intersect pairwise, and no visible text element in the header, layer panel, GPU panel, or popup is clipped (`scrollWidth <= clientWidth` for `.app-title`, `.stress-count`, `.layer-label`, `.gpu-info-panel`). +2. At those three sizes, no panel (`.app-header`, `.layer-panel`, `.gpu-info-panel`, `.feature-popup` when open) extends past the viewport: every rect has `left >= 0`, `top >= 0`, `right <= innerWidth`, `bottom <= innerHeight`. +3. At 375x812 with panels collapsed (layer panel collapsed, no popup), at least 60% of the viewport area is map not covered by the header, layer panel, or GPU panel: `(innerWidth*innerHeight - area(header) - area(layer panel) - area(gpu panel)) / (innerWidth*innerHeight) >= 0.6`. +4. At 375x812, every control is reachable by touch: the layer toggle button, each layer row, the stress slider, and the popup close button are visible, inside the viewport, and the topmost element at their center (`document.elementFromPoint`) is the control or its descendant. +5. The stress count readout fits "5.0M PTS" at every width (issue comment): with the slider at 5,000,000, `.stress-count` has `scrollWidth <= clientWidth` and its right edge is inside `.layer-panel`. +6. Narrow screens (`max-width: 640px`): the layer panel is collapsed by default behind a toggle button in its header. The button is a native ` + ) : ( +
+ SENSOR LAYERS + +
+ )} - {layerList.map(({ id, label }) => { - const active = visibility[id] ?? true - return ( - - ) - })} +