Conversation
Refactored `ChordRow` and `SequenceRow` list items to wrap interactive hit zones in standard `Button` components instead of using `.onTapGesture` on `.contentShape(Rectangle())`. This ensures proper keyboard focus support (via Tab) and allows screen readers to correctly identify the row as a button. Co-authored-by: NSEvent <44446865+NSEvent@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review. 📝 WalkthroughWalkthrough
ChangesAccessible edit controls and diagnostics
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The row edit controls now use native buttons for improved keyboard and screen-reader interaction, with no identified merge-blocking risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Refactored `ChordRow` and `SequenceRow` list items to wrap interactive hit zones in standard `Button` components instead of using `.onTapGesture` on `.contentShape(Rectangle())`. This ensures proper keyboard focus support (via Tab) and allows screen readers to correctly identify the row as a button. Also removed excessive test-deadlocking synchronous debug prints from `MappingEngine.swift`. Co-authored-by: NSEvent <44446865+NSEvent@users.noreply.github.com>
💡 What:
Replaced
.onTapGestureattached toHStackcomponents with standardButtoncomponents inChordRowandSequenceRowlist items. TheHStackis now wrapped inside theButton, with.buttonStyle(.plain)applied to preserve visual styling.🎯 Why:
Attaching
.onTapGestureto non-interactive generic views (likeHStackorVStack) makes them clickable for mouse users but completely hides them from keyboard navigation (Tab key) and screen readers. Wrapping them in a properButtonensures semantic correctness and accessibility.📸 Before/After:
Visual appearance is unchanged.
♿ Accessibility:
PR created automatically by Jules for task 7237675322418955143 started by @NSEvent
Summary by CodeRabbit
Accessibility
Bug Fixes