THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#778 - Clients with nofocus hint but with TAKE_FOCUS protocol doesn't hit
into focus history
User who did this - Uli Schlachter (psychon)
Reason for closing: Fixed
Additional comments about closing: commit
27f9c0177a9d37e5b19732f7e9ff67860ab4bd48
Author: Uli Schlachter <[email protected]>
Date: Sun Aug 15 13:17:07 2010 +0200
Don't call "focus" hook in client_focus()
Later on that call will be done through a FocusIn event.
Signed-off-by: Uli Schlachter <[email protected]>
commit 819daca18c9ad25493e3e7023dd5b107b79683cd
Author: Uli Schlachter <[email protected]>
Date: Fri Apr 6 12:19:12 2012 +0200
Focus history: Don't ignore unfocusable clients
The only caller of focus.history.add() should be the "focus" signal, so at that
time the unfocusable client already does have the focus. At that point,
there is
no reason why this shouldn't be recorded in the focus history.
(And yes, unfocusable clients can be focused. Don't ask.)
This should hopefully fix FS#778.
Signed-off-by: Uli Schlachter <[email protected]>
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=778
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to [email protected].
