Summary: | Gain focus when clicking the maximization button | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | avlas <jsardid> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | nate |
Priority: | NOR | ||
Version: | 5.18.3 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
avlas
2020-03-16 20:06:12 UTC
Since you can click into the window to gain focus, this shouldn't be changed unless it is made configurable. Otherwise, you wouldn't be able to keep the existing behaviour. (In reply to Christoph Feck from comment #1) > Since you can click into the window to gain focus, this shouldn't be changed > unless it is made configurable. Otherwise, you wouldn't be able to keep the > existing behaviour. This requires the counterintuitive process of clicking elsewhere in the window before maximizing. Most of the times the user may not even realize that the window is not on focus in the first place, so the user cannot do that until it's too late (perhaps this is not usually the case for the default breeze decoration, but for most other themes, the difference between active and inactive windows is much more subtle). Furthermore, your response seems to recognize that current behavior may be a feature worth keeping, but I fail to see a use case for maximazing a window that appears below others. If you have some, I'd like to know. I kind of agree, yeah. I also don't see the use case of maximizing a non-active window. The entire point of maximizing a window is to be able to focus on it, instead of other windows. Git commit 73e38aa85966692316d6c4dbc9ae559790bb519c by Benjamin Port. Committed on 17/07/2020 at 09:19. Pushed by bport into branch 'change-maximize-adjust'. When maximizing a window raise client and gain focus M +1 -0 abstract_client.cpp https://invent.kde.org/plasma/kwin/commit/73e38aa85966692316d6c4dbc9ae559790bb519c This bug was reported against an outdated version of KWin. We have made many changes since the. If the issue persists in newer versions can you reopen the bug report updating the version number. |