Repository navigation
Conversation
coffeeneed
approved these changes
Oct 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The window-level
key-press-eventhandler treats Backspace as "go back" (and leaves fullscreen vianormal_mode()). It does this regardless of which widget has focus.When searching channels, pressing Backspace to delete a typo in the search bar also navigates away from the current page, so you can't edit the search query. The same happens in the other text fields of the main window, such as the provider form (name, URL, …) and preferences (MPV options, user agent, …).
The handler now skips Backspace navigation when the focused widget is a
Gtk.Entry, which includes theGtk.SearchEntrysearch bar. The key then reaches the entry and deletes a character as usual. Backspace navigation everywhere else is unchanged.