https://bugs.kde.org/show_bug.cgi?id=501326

Riccardo Robecchi <sephiroth...@hotmail.it> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|REPORTED                    |CONFIRMED

--- Comment #4 from Riccardo Robecchi <sephiroth...@hotmail.it> ---
Changing this to "confirm" given it has been reproduced on Wayland, too.

(In reply to cwo from comment #3)
> I'm not sure about what the correct behavior in general (apart from this
> visual issue) is. On the one hand, having the icon there when it doesn't do
> much feels weird, on the other hand this is a natural consequence of these
> options.  I can see the appeal in the use cases provided in the bug report,
> but this feels a bit like reimplementing a ccustom version offocus stealing
> prevention with virtual desktops, and I'm not sure this is the best design.

I do not see a case in which what we have now is a desirable outcome. I feel
that whatever the chosen approach is, there cannot be a situation in which
clicking on the icon in the task manager does not raise the corresponding
window, because that is simply a broken design. If an exception must be made in
the code in order to make it work, then it should.
It might be a bit of a corner case, but think of a shared computer in which the
"do nothing" option is enabled by one user; another user (as in "person", not
"user account") could try to use the computer and find that they can't activate
a window due to this. Their experience will just feel broken.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to