fix(tag-dropdown): arrow navigation for submenu affecting text input cursor

[icecrasher321]

Summary

Prevent Default in arrow right breaking text input behaviour. This PR finds intuitive way to navigate submenu when open with arrows while maintaining text navigation.

Type of Change

• Bug fix

Testing

Manually. Keep tag dropdown open and text navigation with arrow keys should still work.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
sim	Ready	Preview	Comment	Aug 23, 2025 11:16pm

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Skipped			Aug 23, 2025 11:16pm

[greptile-apps]

Greptile Summary

This PR addresses a UX issue in the tag dropdown component where arrow key navigation was interfering with normal text cursor movement. The problem occurred because the ArrowRight keydown handler always called preventDefault(), which blocked users from moving their cursor within the input field when the dropdown was visible.

The solution introduces a canEnterSubmenuForSelected() helper function that intelligently determines whether the currently selected dropdown item has an available submenu to enter. The ArrowRight handler now only prevents default behavior when there's actually a submenu action available, allowing normal text navigation to occur when no submenu exists.

This change maintains the existing submenu navigation functionality while restoring the expected text editing behavior. The fix is particularly important since the tag dropdown remains open while users type, making cursor navigation within the input field essential for a good user experience. The implementation follows the codebase pattern of using helper functions to extract conditional logic, keeping the main event handler clean and readable.

Confidence score: 4/5

• This PR is safe to merge with minimal risk as it only affects keyboard navigation behavior in a specific UI component
• Score reflects well-structured code changes that preserve existing functionality while fixing a clear UX issue
• Pay close attention to the keyboard event handling logic in the tag dropdown component

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}