When any action is performed outside the input area, the currently focused text box should lose focus.

[sgf]

For example, clicking on a window panel outside the text box should cause the input box to lose focus. However, MewUI currently does not support this.

[al6uiz]

clicking on a window panel outside the text box should cause the input box to lose focus.

This assumption is not correct.

Clicking a non-focusable background area does not necessarily mean the TextBox should lose focus.

WPF behaves the same way. When another focusable control, such as a Button, is clicked, focus moves to that control and the TextBox loses focus. However, clicking a non-focusable area, such as an empty Panel, Grid, or Border, does not automatically clear the current TextBox focus.

For comparison, this WPF file-based app can be run directly from the terminal:

curl -sL https://gist.githubusercontent.com/al6uiz/f5c969fe5a7d51adaad77160f4c0c49f/raw/wpf_focus_repro.cs -o - | dotnet run -

So MewUI should correctly move focus when another focusable element is clicked, but clearing focus on non-focusable background clicks should be an opt-in behavior rather than a global default.

[sgf]

Even if you believe the default UI behavior doesn't need to support this feature, I'd like to provide optional support if possible, since current browsers and most popular software use this behavior. This has one advantage: preventing accidental keyboard input. For example, when I don't want to type, I can simply tap any non-input area to exit input mode.

Another significant advantage is that many applications have shortcut keys. Many applications use keyboard shortcuts that include all 26 letters of the English alphabet.
Furthermore, in many applications, the shortcuts for the input field and the global window are different. For example, in many IM applications, Enter is for sending, while Alt+Enter is for a newline. These shortcuts only apply when the input field is active.

this is wechat

this is github web page

Of course, this is just a suggestion, and you don't necessarily have to accept it.

[al6uiz]

Thanks for the suggestion.

I think this is exactly the kind of topic that is suitable for discussion.

My previous explanation was to clarify that the current behavior follows an intentional and conventional focus model, similar to WPF and Avalonia.

That said, comparing MewUI’s behavior with other applications and discussing whether the focus policy can be improved is a valid direction.

I will consider whether this can be supported in a reasonable way as part of the broader control focus system