QA: test responsive mobile layout on real devices #13

Open
opened 2026-08-07 17:49:33 +02:00 by clawbot · 1 comment
Collaborator

Per the decision in #8, main keeps the responsive mobile layout from #5 (closes #2) rather than a "not available on mobile" message. This issue tracks manual QA of that layout on actual mobile hardware.

What to verify

  • Load the app on a phone (portrait and landscape) and confirm the host-row layout from the max-width: 768px media block in src/styles.css renders correctly
  • Check readability of host rows, status dots, and latency values at narrow widths
  • Rotate the device and confirm the layout reflows sanely across the 768px boundary
  • Confirm polling and gateway detection behave normally on mobile (nothing is skipped — the early-return mobile path from #8 was rejected)
  • Note any layout breakage or unusable interactions as follow-up issues

Ref #2, #5, #8

Per the decision in #8, `main` keeps the responsive mobile layout from #5 (closes #2) rather than a "not available on mobile" message. This issue tracks manual QA of that layout on actual mobile hardware. ### What to verify - Load the app on a phone (portrait and landscape) and confirm the host-row layout from the `max-width: 768px` media block in `src/styles.css` renders correctly - Check readability of host rows, status dots, and latency values at narrow widths - Rotate the device and confirm the layout reflows sanely across the 768px boundary - Confirm polling and gateway detection behave normally on mobile (nothing is skipped — the early-return mobile path from #8 was rejected) - Note any layout breakage or unusable interactions as follow-up issues Ref #2, #5, #8
sneak was assigned by clawbot 2026-08-07 17:49:33 +02:00
Author
Collaborator

Assigning to @sneak: this QA pass needs real physical devices (phones/tablets), which automation here cannot provide. The responsive layout itself landed via PR #5 and the CI gate via PR #12; what remains is hands-on verification on actual hardware. If you find rendering problems, please note device/browser/viewport details here and reassign to clawbot for fixes.

Assigning to @sneak: this QA pass needs real physical devices (phones/tablets), which automation here cannot provide. The responsive layout itself landed via PR #5 and the CI gate via PR #12; what remains is hands-on verification on actual hardware. If you find rendering problems, please note device/browser/viewport details here and reassign to clawbot for fixes.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/netwatch#13