[kwin] [Bug 450405] After moving a native Wayland window to a different virtual desktop it is still considered focused
https://bugs.kde.org/show_bug.cgi?id=450405 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #4 from Oded Arbel --- I think the XWayland comment is very interesting: Wayland window reproduction: you can see that after moving the Wayland window to another desktop, it is still marked as active in the virtual desktop pager widget, but also no window on the current virtual desktop is active: there is definitely only one active window and it is on another desktop. XWayaldn window reproduction: you can see that after moving the XWayland window to another desktop, the XWayland window is *not* marked as active in the virtual desktop pager widget, but no other window - on the current desktop or otherwise - is shown as active: there are now no active windows. That isn't in itself a bug as this is a valid behavior - for example when clicking on the desktop. My main issue with the "move window to another desktop" behavior is that I would have expected one of the windows on the current desktop to become active, possibly in stacking order, but maybe the above behavior is more correct - no window should be active after you moved the current one to a new desktop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450405] After moving a native Wayland window to a different virtual desktop it is still considered focused
https://bugs.kde.org/show_bug.cgi?id=450405 Bacteria changed: What|Removed |Added CC||dev.bacterios...@aleeas.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450405] After moving a native Wayland window to a different virtual desktop it is still considered focused
https://bugs.kde.org/show_bug.cgi?id=450405 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #3 from phrxmd --- I can reproduce this with Kate: if I open Kate on desktop 1, and then use a keyboard shortcut to move it to desktop 2, when I stay on desktop 1 and continue typing the Kate window on desktop 2 receives my keyboard input. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450405] After moving a native Wayland window to a different virtual desktop it is still considered focused
https://bugs.kde.org/show_bug.cgi?id=450405 postix changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=444172 Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DUPLICATE |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450405] After moving a native Wayland window to a different virtual desktop it is still considered focused
https://bugs.kde.org/show_bug.cgi?id=450405 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450405] After moving a native Wayland window to a different virtual desktop it is still considered focused
https://bugs.kde.org/show_bug.cgi?id=450405 --- Comment #2 from Firlaev-Hans --- I do not believe this is a duplicate of the bug you linked, at least not exactly. At the very least, the fix for the ghost window bug in 5.24.1 did not fix this bug. It seems likely that this bug was the root cause for the ghost windows bug; Since the native Wayland window is still "focused" after leaving the workspace it would still be drawn, or at least its area would not be repainted, until you actively focus something else. But the ghost window bug ended up getting fixed by repainting the workspace after a window leaves the VD, which only fixed the symptom and not the root cause. So while we no longer get the visual artifact, the window is still considered the focused window by KWin and receives keyboard input while on a different workspace, even in the latest Plasma version. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450405] After moving a native Wayland window to a different virtual desktop it is still considered focused
https://bugs.kde.org/show_bug.cgi?id=450405 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 444172 *** -- You are receiving this mail because: You are watching all bug changes.
