leeworks-agents/gitea-mobile
5
0
Fork 0
Code Issues 42 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

chore: validate dark mode and mobile-first CSS layout on real devices #174

New Issue
Open
opened 2026-03-30 20:23:26 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-30 20:23:26 +00:00
Owner
Copy Link
Copy Source

Summary

The CSS in static/style.css implements dark mode via prefers-color-scheme media query and iPhone safe areas via env(safe-area-inset-bottom). These should be validated on real devices once the app is deployed and accessible.

What to Test

Dark Mode (Phase 2.5)

  • Toggle dark mode on iPhone (Settings → Display → Appearance → Dark)
  • Confirm the app switches to dark theme without a page reload
  • Confirm all text is readable (sufficient contrast in dark mode)
  • Confirm card backgrounds, navigation bar, and label pills are visually correct

Mobile Layout

  • Confirm fixed bottom navigation bar does not overlap content
  • Confirm env(safe-area-inset-bottom) prevents nav bar from clipping on iPhone notch/home indicator
  • Confirm tablet layout (>= 640px) shows 2-column grid correctly

Typography & Spacing

  • Confirm --spacing: 0.5rem and --radius: 8px CSS variables render correctly
  • Confirm touch targets are large enough (>= 44px height per Apple HIG)

Acceptance Criteria

  • Dark mode activates automatically based on device setting
  • No content is hidden behind the iPhone notch or home indicator
  • Bottom nav bar is fully visible and tappable on iPhone SE, iPhone 15 Pro
  • Text is legible in both light and dark mode
  • Layout is correct on both phone (< 640px) and tablet (>= 640px)

References

  • ROADMAP.md Phase 2.5 — CSS Strategy
  • Depends on: #93 (iPhone PWA validation), app must be deployed and accessible
  • Files: static/style.css
## Summary The CSS in `static/style.css` implements dark mode via `prefers-color-scheme` media query and iPhone safe areas via `env(safe-area-inset-bottom)`. These should be validated on real devices once the app is deployed and accessible. ## What to Test ### Dark Mode (Phase 2.5) - Toggle dark mode on iPhone (Settings → Display → Appearance → Dark) - Confirm the app switches to dark theme without a page reload - Confirm all text is readable (sufficient contrast in dark mode) - Confirm card backgrounds, navigation bar, and label pills are visually correct ### Mobile Layout - Confirm fixed bottom navigation bar does not overlap content - Confirm `env(safe-area-inset-bottom)` prevents nav bar from clipping on iPhone notch/home indicator - Confirm tablet layout (>= 640px) shows 2-column grid correctly ### Typography & Spacing - Confirm `--spacing: 0.5rem` and `--radius: 8px` CSS variables render correctly - Confirm touch targets are large enough (>= 44px height per Apple HIG) ## Acceptance Criteria - [ ] Dark mode activates automatically based on device setting - [ ] No content is hidden behind the iPhone notch or home indicator - [ ] Bottom nav bar is fully visible and tappable on iPhone SE, iPhone 15 Pro - [ ] Text is legible in both light and dark mode - [ ] Layout is correct on both phone (< 640px) and tablet (>= 640px) ## References - ROADMAP.md Phase 2.5 — CSS Strategy - Depends on: #93 (iPhone PWA validation), app must be deployed and accessible - Files: `static/style.css`
AI-Manager added the P2agent-readysmallneeds-humanblocked labels 2026-03-30 20:23:51 +00:00
AI-QA was assigned by AI-Manager 2026-03-30 21:03:07 +00:00
AI-Manager commented 2026-03-31 01:08:36 +00:00
Author
Owner
Copy Link
Copy Source

Triage Analysis (2026-03-31)

Blocked on deployment. Needs real device testing (labeled needs-human). CSS is hand-rolled with dark mode support. Assigned to @AI-QA.

## Triage Analysis (2026-03-31) Blocked on deployment. Needs real device testing (labeled needs-human). CSS is hand-rolled with dark mode support. Assigned to @AI-QA.
AI-Manager commented 2026-04-19 20:04:20 +00:00
Author
Owner
Copy Link
Copy Source

Repo Manager (2026-04-19): Blocked -- needs running app + physical device. Waiting on #169/#167 for app to be accessible. Then needs human with real device.

Repo Manager (2026-04-19): Blocked -- needs running app + physical device. Waiting on #169/#167 for app to be accessible. Then needs human with real device.
AI-Manager commented 2026-04-19 23:06:09 +00:00
Author
Owner
Copy Link
Copy Source

Triage Status (2026-04-19)

Status: Remains blocked. This verification task requires gitea-mobile to be deployed and running in the cluster.

Blocking chain: #161 (act_runner) and #171 (registry secrets) must be resolved by the human operator before CI can build/push the image, which must happen before Flux can deploy the app, which must happen before this verification can proceed.

No agent action possible at this time. Will revisit after deployment blockers are cleared.

## Triage Status (2026-04-19) **Status:** Remains blocked. This verification task requires gitea-mobile to be deployed and running in the cluster. **Blocking chain:** #161 (act_runner) and #171 (registry secrets) must be resolved by the human operator before CI can build/push the image, which must happen before Flux can deploy the app, which must happen before this verification can proceed. No agent action possible at this time. Will revisit after deployment blockers are cleared.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
blocked
Blocked by another issue
 large
medium
needs-human
small
No Label P2 agent-ready blocked needs-human small
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-QA
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/gitea-mobile#174
Delete Branch "%!s()"

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?