Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When using @ Symbols, in the chat, the hovered item takes precedence over the keyboard input #1418

Open
dgokcin opened this issue Apr 25, 2024 · 0 comments

Comments

@dgokcin
Copy link

dgokcin commented Apr 25, 2024

Description: When using the cursor app, I noticed inconsistent behavior regarding keyboard input and mouse interaction in different menus.

Steps to Reproduce:

  1. Open the desktop app.
  2. Navigate to Go to File with Command + P.
  3. Hover the mouse cursor over an item in the list and close the menu
  4. Press Command + P to initiate the same flow.
  5. Enter keystrokes(a file name) and oberve the behavior.
  6. Do the same thing for the chat with Command + L and hover on something.
  7. Close the menu and type Diff and try selecting @Diff of Working State + <Enter>
  8. Observe the difference

2024-04-25 08 47 28

Expected Behavior:

  • When using Command + P, the keyboard input should take precedence over the mouse cursor, even if the cursor is hovering over an item in the list. The item under the cursor should not be selected until explicitly clicked.

Actual Behavior:

  • In the specified menu or area, the mouse cursor's position takes precedence over keyboard input. If the mouse cursor is hovering over an item in the list, that item is selected instead of the one matching the keystrokes entered after pressing Command + L.

Cursor & OS Information

Version: 0.32.2
VSCode Version: 1.86.2
Commit: f8ed437267c50dbc975beb3d51f89c800277bb30
Date: 2024-04-17T09:01:02.813Z
Electron: 27.2.3
ElectronBuildId: undefined
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin arm64 23.4.0

Additional Notes:

  • This behavior is inconsistent with other parts of the application, where keyboard input correctly takes precedence over mouse interaction.
  • The issue persists even after restarting the application.
  • This behavior makes it difficult to efficiently use @ symbols in the chat menu
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

No branches or pull requests

1 participant