Fix Find in File search field being unclickable after Enter in Vim mode

[warp-agent-staging]

Description

With Vim mode enabled, pressing Enter in the code editor's Find in File field left the field stuck at InteractionState::Disabled. A disabled editor element ignores mouse events (EditorElement::mouse_down returns early when !can_select), so the only way to edit the query again was to reopen the bar with Cmd/Ctrl+Shift+F. The same dead-end applied to the field left disabled by Vim's * / # (search_word_at_cursor).

The disabled state is load-bearing — it is what routes subsequent keystrokes to Vim instead of the find input (the VimUserTyped guard in code/editor/view/actions.rs) and what dims the committed query — so this keeps it and instead makes a click re-activate the field.

Changes

• Added FindAction::FocusFindInput, dispatched from a Hoverable wrapped around the find input in CodeEditorFind::render_find_row. The handler is a no-op while the input is editable, so ordinary click-to-place-caret behaviour in the find field is unchanged.
• Extracted CodeEditorFind::activate_find_input (make editable, select the query, focus) and reused it from both the new action handler and View::on_focus, which previously inlined the same logic.
• Gave the find input a SavePosition (mirroring the existing case_sensitive_button one in the same view) so its bounds can be resolved for mouse events.
• Vim behaviour is otherwise untouched: Enter still commits the query and moves the caret into the editor, n/N still cycle, and the non-Vim Enter path (advance to next match) and the terminal find bar are not on this code path.

Linked Issue

CODE-1943

Testing

Two regression tests in app/src/code/editor/view/vim_handler_tests.rs cover the Vim Enter path and the Vim * path. Both drive the real user path rather than the action handler: they render the code editor and its find bar into a Presenter and dispatch a LeftMouseDown/LeftMouseUp pair at the find input's painted bounds, then assert the input is focused and editable. The Enter case additionally dispatches TypedCharacters through the window and asserts the query became eta while the buffer and the Vim mode were untouched — had Vim received those keystrokes, a would have switched it to Insert mode.

Each test was verified to fail in two ways and pass with the change intact:

• with the FocusFindInput handler neutralized (the fix itself), and
• with the Hoverable's on_mouse_down wiring removed, which confirms the click really travels through the new wrapper rather than being simulated.

Checks run:

• ./script/format
• cargo clippy -p warp --all-targets --tests -- -D warnings and the same with --features tui (matching the workspace feature unification) — clean
• cargo nextest run -p warp code::editor:: — 116 passed
• cargo nextest run -p warp find — 120 passed

Manual verification with the locally built client (cargo run --bin warp) on Linux, with Vim keybindings enabled, on a file opened in the code editor:

1. / opens Find in File, typing hello shows 3/3 and highlights the three matches.
2. Enter dims the query, removes the caret from the field, and moves the file cursor to the active match.
3. Clicking the query text re-activates the field — the query becomes selected and the field is editable again.
4. Typing eta replaces the query, the counter updates to 1/4, and the highlights follow. Enter re-commits, and clicking once more re-activates the field again.

• I have manually tested my changes locally

Screenshots / Videos

Computer-use video recordings

Find in File flow in Warp code editor: Opening the Find in File popup in Warp's code editor, typing the query "hello", pressing Enter, then clicking back into the find field and editing the query to "helloeta" and pressing Enter again.

Computer-use screenshots (4)

Find in File popup after typing "hello" (before Enter): field shows "hello" with caret, counter reads 3/3, and "hello" is highlighted on lines 2, 3, and 5.

Find popup immediately after pressing Enter: the query "hello" is dimmed/grey with no visible caret (inactive/committed field), counter still 3/3, and the file cursor has moved to line 5.

Find popup after clicking back into the search field: the query "hello" is now selected/highlighted with a blue selection background, indicating the field is active again.

Find popup after typing "eta" (which replaced the selected "hello"): field shows "eta" with caret, counter reads 1/4, and "eta" is highlighted within beta (line 1, active), zeta and standalone eta (line 3), and theta (line 4).

Agent Mode

• Warp Agent Mode - This PR was created via Warp's AI Agent Mode

Conversation: https://staging.warp.dev/conversation/40763365-157a-4144-a562-828a8fa58ee9
Run: https://oz.staging.warp.dev/runs/019fddcd-625c-7bb8-a71e-ad8aa35b1614

This PR was generated with Oz.