[Wayland-bugs] [Bug 73905] Weston clients receive key events while Weston is locked

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Apr 10 09:48:15 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=73905

Kristian Høgsberg <krh at bitplanet.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Kristian Høgsberg <krh at bitplanet.net> ---
Committed to master:

commit 4237f50e11826445319864518289ba1733e11223
Author: Neil Roberts <neil at linux.intel.com>
Date:   Wed Apr 9 16:33:31 2014 +0100

    Reset focus on unknown seats when restoring focus state

    The focus_state list on a workspace only contains entries for seats
    which have a keyboard focus on that workspace. For workspaces that
    have no surfaces the list will be empty. That means that when a
    workspace with no surfaces is switched to it would previously leave
    the keyboard focus unaffected and you could still type in the surface
    on the old workspace.

    This patch makes it instead reset the keyboard focus to NULL for seats
    without a focus_state. It does this by temporarily stealing the
    compositor's list of seats while it iterates the focus_states. After
    all of the focus states have been processed any seats remaining in
    this temporary list have their focus reset.

    https://bugs.freedesktop.org/show_bug.cgi?id=73905

and

commit b4a91708e3c440e2d56d476ce71e82af8f79563f
Author: Neil Roberts <neil at linux.intel.com>
Date:   Wed Apr 9 16:33:32 2014 +0100

    Reset the keyboard focus on all seats when the compositor is locked

    Before commit 2f5faff7f9142 when the compositor is locked it would
    reset the keyboard focus on all of the seats as part of pushing the
    focus_state. This was removed because it now always keeps track of the
    focus_state in the workspace instead of waiting until the state is
    pushed. However this had the side effect that the active surface would
    retain focus when the compositor is locked. This patch just makes it
    explicitly set the keyboard focus to NULL on all of the seats when
    locking. This will be restored based on the workspace's state when
    unlocking.

    https://bugs.freedesktop.org/show_bug.cgi?id=73905

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20140410/4aeea57d/attachment.html>


More information about the Wayland-bugs mailing list