Fix request type visibility, mobile layout overflow, and overnight polling (#23, #24, #25)

[pataniaeli]

Fixes #23, #24, and #25.

#25 — User reports high usage overnight

Rather than guess at a polling bug, I checked the actual Supabase request logs (edge_logs, filtered to the service-role/node user agent) for the overnight window. Two spaces' /display/[spaceId] kiosk pages were each generating ~270 identical requests to spaces/space_bookings/space_blackouts over 16 hours — continuous polling every 50s regardless of whether anyone could see the screen. That matches the reported Screen Time chart exactly: solid, uninterrupted usage attributed to the site across 12AM–5AM.

Fix: both the 50s data poll and the 1s clock tick now check document.visibilityState before doing anything, so a display left open in a backgrounded tab (screen off, phone locked, tab switched away) stops generating traffic. A visibilitychange listener fetches immediately on return so it catches up rather than waiting out the interval. A kiosk whose screen genuinely stays on the whole time — the feature's actual use case — is unaffected.

#23 — Request types not visible or filterable

Requests have carried scope/division/room_request_bodies since #19, but nothing rendered it anywhere. Added:

• scope, division, and room_request_bodies(body_id, bodies(name)) to the /api/administrator/requests and /api/me/requests selects.
• ScopeLabel (already used for bookings) on every request surface: the admin Requests tab, the Fulfill Request modal, the Open Requests sidebar in all three admin creation forms, and leadership's own My Requests list.
• A type filter (All / Single Body / Divisional / Multi-Body) on the admin Requests tab and each Open Requests sidebar, alongside their existing filters.

#24 — Mobile layout clipping and overflow

Traced each of the seven reported symptoms to a specific cause rather than a general responsive pass:

• The fixed mobile hamburger button reserves no layout space; two of the reported screens had a right-aligned control sitting directly underneath it. Content now gets pt-20 clearance on mobile.
• My Rooms' header row now wraps instead of forcing the day-range buttons against the notification bell.
• The notification dropdown's fixed w-80 overflowed off-screen since the bell sits near the left of its row — clamped to the viewport.
• Settings' "Add a body" <select> hit the classic flexbox min-width: auto gotcha (pinned to its widest <option>, ignoring flex-1) and pushed the Join/Request button off-screen — same root cause broke the Weekly Room Start/End Date fields in the request form.
• The request-a-booking type tabs didn't scroll, hiding the "Viewing Previous Requests" toggle — now uses the same overflow-x-auto pattern already established for the Administrator tab bar (Administrator Tab will not scroll on mobile #10).
• SGA Spaces' range filter buttons now wrap instead of running off the page; the blackout create/edit forms' Date+Time grid stacks to one column below sm instead of cramming a 3-select TimePicker into half a row; Active Blackouts was overflow-hidden (clipping) instead of overflow-x-auto (scrollable).

Verification

tsc --noEmit clean, npm run build compiles all 61 routes. Lint on the touched files shows only three pre-existing setState-in-effect errors in code I didn't modify (confirmed via git diff that none of my changes touch those effects) — no new errors or warnings introduced.

I did not do a live authenticated click-through of the mobile fixes in a browser — verification here is build/typecheck plus a careful read of each fix against the reported screenshot. Worth a manual pass on a real phone before merging, particularly the notification dropdown clamp and the blackout form stacking.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
chambers	Ready	Preview	Aug 26, 2026 2:48pm