Clarity for controls - #735
Conversation
|
Warning Review limit reached
Next review available in: 52 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
📝 WalkthroughWalkthroughThe player controls UI now displays keyboard bindings, translated titles, controller mappings, and updated camera instructions across supported locales. Key styling was refined. Eye-gizmo cleanup and activation now update orbit status messages. ChangesPlayer controls UI
Eye-gizmo status handling
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@accessibility/keyboardui.js`:
- Around line 1199-1210: Update renderControl in the entry.marks branch so the
sr-only accessible text includes entry.keys when present, alongside entry.label;
preserve the current label-only output when no keys exist and keep the visual
aria-hidden markup unchanged.
In `@locale/de.js`:
- Around line 1224-1242: Add the missing Player panel key-label translations to
each locale file. The keys player_decrease_font_size, player_increase_font_size,
gamepad_left_stick, gamepad_right_stick, gamepad_l1_r1, gamepad_triangle_y,
gamepad_square_x, gamepad_circle_b, gamepad_cross_a, dpad_up, dpad_down, and
dpad_left are referenced by accessibility/keyboardui.js but not defined in these
locale objects, causing fallback to English. Add these translations in the
Player panel section at locale/de.js lines 1224-1242, locale/fr.js lines
1231-1250, locale/it.js lines 1233-1252, locale/pl.js lines 1225-1244,
locale/pt.js lines 1236-1254, and locale/sv.js lines 1211-1229.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 12635010-f981-40dc-adcb-28c465d20072
📒 Files selected for processing (11)
accessibility/keyboardui.jslocale/de.jslocale/en.jslocale/es.jslocale/fr.jslocale/it.jslocale/pl.jslocale/pt.jslocale/sv.jsstyle.cssui/gizmos.js
Summary
AI usage
Claude Sonnet 5 and Haiku 4.5 used throughout, plans made by me.
Summary by CodeRabbit