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

Vlad Zahorodnii <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |RESOLVED
         Resolution|---                         |UPSTREAM

--- Comment #3 from Vlad Zahorodnii <[email protected]> ---
> If the token request carries a surface that is already mapped, this is a
> window-activation request

That surface is rather a hint for the compositor to indicate the activation
token origin surface. It is not the same as the surface that is going to be
activated. For example, the requesting surface can be the panel surface.

On the compositor side, we don't have enough information to determine whether
it's an activation or launch so we show the bouncy icon all the time (unless
StartupNotify is false of course)

. (In reply to Daniil Aleksashin from comment #2)
> (In reply to David Redondo from comment #1)
> > we dont know if the application will launch a new window or even instance or
> > activate an existing one.
> 
> That's why there should be a distinction, no?

Yes, but the changes need to happen upstream.

---

Would you mind filing an upstream issue?

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

Reply via email to