fix(seer-agent): fix showActions on hover and cleanup broken focusedBlockIndex state#113739
fix(seer-agent): fix showActions on hover and cleanup broken focusedBlockIndex state#113739
Conversation
| if (focusedBlockIndex !== -1) { | ||
| setFocusedBlockIndex(-1); | ||
| if (hoveredBlockIndex !== -1) { | ||
| setHoveredBlockIndex(-1); |
There was a problem hiding this comment.
Hover state cleared by typing, won't restore without mouse re-enter
Medium Severity
handleInputChange resets hoveredBlockIndex to -1 whenever the user types, which was logic designed for the old keyboard-focused focusedBlockIndex paradigm. Now that the state is driven by mouse hover, if a user's mouse is resting over a block while they type in the textarea, each keystroke clears the hover state (hiding action buttons). Since onMouseEnter only fires when the cursor enters an element (not while stationary inside it), the hover state won't restore until the mouse physically leaves and re-enters the block. The textareaRef.current?.focus() call is also redundant here since the textarea is already focused (the user is typing in it).
Reviewed by Cursor Bugbot for commit 2c73298. Configure here.
There was a problem hiding this comment.
theres no way to focus the input now without clicking it
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
There are 2 total unresolved issues (including 1 from previous review).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit b88fb59. Configure here.
| blocks: Block[]; | ||
| focusedBlockIndex: number; | ||
| isOpen: boolean; | ||
| setFocusedBlockIndex: (index: number) => void; |
There was a problem hiding this comment.
Unused required props in useBlockNavigation hook interface
Low Severity
UseBlockNavigationProps still declares blockRefs and blocks as required props, and isMinimized and onNavigate as optional props, but the hook body no longer destructures or uses any of them. The call site in explorerDrawerContent.tsx still passes all four. This is dead code left over from removing the arrow-key navigation logic.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit b88fb59. Configure here.


also fixes block navigation, disabling it when input is focuseddeletes block keyboard nav for now, except pressing enter