https://bugs.kde.org/show_bug.cgi?id=443237
Bug ID: 443237
Summary: focusing a window (with hover to focus) should not
change its order on the "recently used" stack
Product: kwin
Version: 5.22.4
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: adam.m.fontenot+...@gmail.com
Target Milestone: ---
SUMMARY
This is a nit, but a major pain point for those using the "focus follows mouse"
setting (in Settings > Window Management > Window Behavior > Window activation
policy). When you briefly hover over an inactive window, but do not otherwise
interact with it, KWin raises the window to the top of its *internal* stack of
windows - it doesn't raise the window to the top of the visible windows *on the
screen*, but it otherwise behaves as if it *had* done so.
STEPS TO REPRODUCE
1. Set focus follows mouse (mouse precedence) as your window activation policy.
Delay focus is 0ms, Focus stealing prevention is Medium.
2. Open three windows. One should be maximized (your browser works fine), two
should be small windows some distance apart from each other, and both of these
should be on top of the maximized window.
3. Click on one of the small windows to focus it. Move the cursor to the other
window (*passing over the background window*) and click on the other window.
4. Press alt-tab (or whatever shortcut you have to activate the task switcher).
OBSERVED RESULT
The window that the task switcher tries to activate is the background window,
even though you never interacted with it or tried to raise it.
EXPECTED RESULT
The other small window should be selected by the task switcher.
This is a very common pattern. You have something like your browser running
maximized, and meanwhile you're working with two windows (say, a terminal and a
code editor), and you need to copy something from one of these windows and
paste it in the other. You try to alt-tab back to the initial window, but
unfortunately the brief moment when the background window was focused was
enough for KWin to move it to the top of the stack.
Important note: I'm aware that the task switcher has a "stacking order" option.
This seemingly does the *opposite* of what I want. When I am in a window on the
top of the visible stack, and I alt-tab to go back to the previous window I was
using, "stacking order" starts me at the *bottom* of the stack and moves up
from there!
I think it's sensible to have this option for people who want it (after all, if
you're not using hover to focus then if "stacking order" worked in top-down
fashion then it would - I think - behave identically to "recently used"). So I
think the most reasonable understanding of this problem is as a bug in hover to
focus: a window should not be considered recently used just because it was
focused: it should only be recently used if I interacted with it, e.g. raised
it by clicking.
SOFTWARE/OS VERSIONS
Linux: Arch Linux x86_64 (kernel 5.14.5)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
--
You are receiving this mail because:
You are watching all bug changes.
