https://bugs.kde.org/show_bug.cgi?id=424223
Vlad Zahorodnii <vlad.zahorod...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit| |https://invent.kde.org/plas
| |ma/kwin/commit/271725286104
| |8794737f6aa72c9054840481474
| |6
Version Fixed In| |5.19.4
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Vlad Zahorodnii <vlad.zahorod...@kde.org> ---
Git commit 2717252861048794737f6aa72c90548404814746 by Vlad Zahorodnii.
Committed on 21/07/2020 at 09:56.
Pushed by vladz into branch 'master'.
Partially revert a0c4a8e766a2160
Unfortunately, a0c4a8e766a2160213838daf6f71c7ae6c3705df has a major bug
where clients that track focus events may get confused by focusToNull().
One such a notable example is Dota 2. It tracks the focus events to
minimize itself after the keyboard focus has been lost as well stop
playing music while it's in background. So, when we call focusToNull(),
Dota 2 will receive a corresponding FocusOut event and ask the window
manager to minimize it. It doesn't really matter that the FocusOut
event is going to be followed by a FocusIn event because when a window
is minimized, kwin will activate the next one in the focus chain.
Since those issues can't be fixed from the window manager's side, this
patch partially reverts a0c4a leaving only the autotest.
FIXED-IN: 5.19.4
M +2 -0 autotests/integration/x11_client_test.cpp
M +0 -5 x11client.cpp
https://invent.kde.org/plasma/kwin/commit/2717252861048794737f6aa72c90548404814746
--
You are receiving this mail because:
You are watching all bug changes.
