input: no extra key processing in alternate input modes

In 3a2eb80d83, we fixed an issue where
key *releases* triggered a selection reset, and viewport reset.

The same issue still exists in other input modes (unicode, search and
url mode); if the kitty keyboard protocol has been enabled, with
release events, any key press directed to e.g. search input handling,
will was not remembered, and the corresponding release event generated
a kitty keyboard event to the terminal application, and reset the
viewport and selection.

This means, for example, that scrollback search was unusable.

Fix by *never* doing any further (generic) key processing if an
alternate input mode is active.

Closes #2316
This commit is contained in:
Daniel Eklöf 2026-04-06 10:45:43 +02:00
parent 46a9cb8aab
commit 89d6ff10fa
No known key found for this signature in database
GPG key ID: 5BBD4992C116573F
2 changed files with 15 additions and 8 deletions

View file

@ -78,8 +78,12 @@
* Other output (key presses, query replies etc) being mixed with paste
data, both interactive pastes and OSC-52 ([#2307][2307]).
* Scrollback search not working correctly when the terminal
application has enabled the kitty keyboard protocol with release
event reporting ([#2316][2316]).
[2307]: https://codeberg.org/dnkl/foot/issues/2307
[2316]: https://codeberg.org/dnkl/foot/issues/2316
### Security