https://bugs.kde.org/show_bug.cgi?id=506324
--- Comment #4 from Nicolas Fella <[email protected]> --- > Moreover, i think edge cases may need plasma help to function properly, for > example: when raising a player running in another virtual desktop, raise > should either: > - switch to the VD containing the player window virtual and put the player > window in the foreground > - or bring the player window into the current VD and put the player window in > the foreground. That will work automatically if the window properly activates itself > I think this is needed for the application to raise itself up (make raise > work in exactly the same application controlled way in every Wayland > compositor) but from my reading of the raise method it is not mandatory that > the application raise itself and most/all of them don't, plasma could detect > the dbus signal and take appropriate step to put the player window in focus. Raise doesn't necessarily make sense for every player, imaging a background daemon without any windows. Also, in order to do what you are describing Plasma would need to "guess" which window(s) belong to a player and which one should be raised. Not very reliable so I'd rather not do that -- You are receiving this mail because: You are watching all bug changes.
