fix: accidentally leaving the mouse over autocomplete items highlights them

[heyseth]

Related GitHub Issue

Closes: #8615

Description

This PR separates hover state from keyboard selection state in the context menu autocomplete to prevent mouse hover from interfering with keyboard navigation.

Key implementation details:

• Introduced hoveredIndex state separate from selectedIndex to track mouse hover independently
• selectedIndex is now only updated by keyboard navigation and onClick events
• hoveredIndex is updated by onMouseEnter/onMouseLeave for visual hover feedback

Design rationale:
I implemented this to exactly mimic VSCode's Quick Open/Command Palette behavior, where:

• Keyboard navigation (arrow keys) maintains its own selection state
• Mouse hover provides immediate visual feedback without affecting keyboard selection
• Pressing Enter selects the keyboard-selected item, not the hovered item
• Clicking with the mouse properly updates selection before triggering the action

Test Procedure

Manual testing steps:

1. Position the mouse cursor above the chat input so that it will be hovering over a context menu item when the menu appears
2. Open the context menu by typing @ in the chat input
3. Verify that the hovered over menu item shows hover styling
4. Use arrow keys to navigate through menu items - verify the selection moves correctly
5. Move the mouse to hover over a different menu item - verify it shows hover styling
6. While hovering over one item, use arrow keys to select a different item
7. Press Enter - verify it selects the keyboard-selected item, NOT the hovered item
8. Re-open the context menu
9. Hover over a menu item and click it - verify it selects the mouse-selected item and triggers correctly

Expected behavior:

• Hover styling appears immediately when mouse enters an item
• Keyboard selection (solid highlight) is independent of mouse hover (lighter highlight)
• Enter key always selects the keyboard-selected item
• Mouse click properly selects and triggers the clicked item

This matches the exact behavior of VSCode's native Quick Open (Ctrl+P) and Command Palette (Ctrl+Shift+P) menus.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Documentation Updates

• No documentation updates are required.

Get in Touch

Discord: @ocean.smith

---

Important

Separates hover and selection states in ContextMenu.tsx to prevent mouse hover from interfering with keyboard navigation.

• Behavior:
  • Introduces hoveredIndex state in ContextMenu.tsx to track mouse hover separately from selectedIndex.
  • selectedIndex updated only by keyboard and onClick events.
  • hoveredIndex updated by onMouseEnter/onMouseLeave for hover feedback.
• Design:
  • Mimics VSCode's Quick Open behavior: keyboard and mouse interactions are independent.
  • Enter key selects keyboard-selected item; mouse click selects hovered item.
• Visual Feedback:
  • Different styles for keyboard selection and mouse hover in ContextMenu.tsx.

^{This description was created by for eac11c1. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Rooviewer   See task on Roo Cloud

Review complete. No issues found.

This PR successfully separates hover and selection states in the context menu, preventing mouse hover from interfering with keyboard navigation. The implementation correctly mimics VSCode's Quick Open behavior.

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[roomote]

Rooviewer   See task on Roo Cloud

Review complete. No issues found.

This PR successfully separates hover and selection states in the context menu, preventing mouse hover from interfering with keyboard navigation. The implementation correctly mimics VSCode's Quick Open behavior where keyboard and mouse interactions are independent.

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}