https://bugs.kde.org/show_bug.cgi?id=503669
Bug ID: 503669
Summary: Focus switch between windows happens on mouse button
press in some cases, release in others, and when the
latter, creates furher inconsistencies
Classification: Plasma
Product: plasmashell
Version: 6.3.4
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: php4...@gmail.com
CC: k...@davidedmundson.co.uk
Target Milestone: 1.0
SUMMARY
When a window A has focus, and you click on the title bar of another window B,
the focus switches immediately when you press the button, not when you release
it, which is nice. So for example if you press the button on window B's title
bar and start dragging it around, the new window is immediately brought on
front as soon as you press, i.e. as soon as you start dragging.
On the other hand, if you click anywhere else on window B, something strange
happens.
At the moment you press, the old window A remains on front, the new window B
remains behind, but there's some sort of animation where you seem to see the
focus going from A to B. If pressing and holding the button and moving the
mouse cursor has some effect on window B (e.g. selecting text, navigating a
menu, or dragging the scrollbar to scroll window B), you see that effect, that
is, you are already fully interacting with window B, even though it's behind
window A. Only when you release the mouse button does window B come on front
and clearly fully become the foreground focused window.
One particularly absurd situation is the one shown in the attached screenshot,
where I pressed and held the button over a menu of the unfocused window B
(Filezilla): window B (FileZilla) is behind, window A (Kate) is on the
foreground, but window B's menu is on top of window A: this is a completely
impossible, nonsensical situation. Any menu, submenu, popup or appendix of any
kind belonging to window A should always be strictly on top of A and strictly
behind anything that is on top of A.
Traditionally, there's always been a tendency to react to clicks on release
rather than on press, and I guess there are good reasons beyond pure
convention, but in this case, given that:
(A) there are very strong reasons for switching focus on press in at least some
particular cases, such as the case where you drag a window, and
(B) in the remaining cases, a mouse press often initiates some kind of
interaction with the newly-clicked window (e.g. text selection, submenu
navigation, scrollbar scrolling),
there's a very compelling reason for always switching the focus on press rather
than on release; or in other words, when the interaction with the new window
begins and not when it ends.
SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.6.85-2-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 12 × 12th Gen Intel® Core™ i7-1255U
Memory: 15.3 GiB of RAM
Graphics Processor: Intel® Iris® Xe Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: Vivobook_ASUSLaptop X1502ZA_F1502ZA
System Version: 1.0
--
You are receiving this mail because:
You are watching all bug changes.
