Repository navigation
Conversation
Keep descendant focus when a mouse event originated from a descendant, instead of moving keyboard focus to the receiving container. Continue to focus the container for direct clicks or when focus is outside its subtree.
Descolada
marked this pull request as ready for review
October 27, 2026 12:31
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
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.
A mouse event from a TextArea inside a TabControl can bubble to the GTK Notebook handler. Its automatic focus grab then moves focus to the Notebook, so subsequent typing no longer reaches the TextArea. It also overrides a MouseDown handler that focuses another descendant.
Preserve focus when both the original event widget and the focused widget are descendants of the receiving control. Direct container clicks and focus outside the subtree retain the existing focus behavior.