Skip to content

fix(mobile): collapse HUDs so the track stays clear at 320px#8

Merged
shaal merged 1 commit into
mainfrom
fix/mobile-narrow-hud-collapse
Jul 23, 2026
Merged

fix(mobile): collapse HUDs so the track stays clear at 320px#8
shaal merged 1 commit into
mainfrom
fix/mobile-narrow-hud-collapse

Conversation

@shaal

@shaal shaal commented Jul 23, 2026

Copy link
Copy Markdown
Owner

Summary

Phone-width layout (≈320px) was burying the track under stacked chrome: metrics HUD + cinema HUD/story, the phase banner, the full Follow/3D/Trails/Heat/Rays/Demo chip row, and help FABs.

Changes (≤480px)

  • Hide #metrics-hud (duplicates cinema stats)
  • Compact cinema HUD to Gen / Alive / Best; hide story + Laps/Sim chips
  • Hide #bottomText phase banner
  • Collapse cinema view chips behind a Views / Hide toggle (default collapsed)
  • Move help FABs to a smaller top-right stack
  • Top-align the 16:9 canvas so overlays sit on the frame instead of empty space above a centered track

Validation

  • agent-browser viewport 320×700: metrics display: none, only Views visible until expanded, canvas top-aligned, FABs at top-right

Test plan

  • agent-browser @ 320×700 before/after screenshots
  • Views expand shows Follow/3D/Trails/Heat/Rays/Demo
  • Hard-refresh on a real phone and confirm track is readable mid-training
  • Desktop (≥481px) still shows full cinema chips with no Views toggle

On narrow viewports, hide the redundant metrics HUD and phase banner,
compact the cinema stats, collapse view chips behind a Views control,
and park help FABs in a top-right stack so chrome no longer covers the
track.
@shaal
shaal merged commit 44d55da into main Jul 23, 2026
@shaal
shaal deleted the fix/mobile-narrow-hud-collapse branch July 23, 2026 23:07
@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@shaal, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 41 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c214a49e-1a77-4f79-a714-838138a9b355

📥 Commits

Reviewing files that changed from the base of the PR and between 057f3c3 and dc1e8a7.

📒 Files selected for processing (2)
  • AI-Car-Racer/demoPresentation.js
  • AI-Car-Racer/style.css
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/mobile-narrow-hud-collapse

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant