[PATCH wayland-protocols 2/4 v2] xdg-shell: Clarify focus semantics for popup grabs

[Jonas Ådahl]

Make it clearer what the focus semantics are during a popup grab. In
short, when a grabbing popup is mapped, the top most popup will always
have keyboard focus, while pointer and touch focus works just as normal
except that only surfaces from the grabbing client will receive pointer
and touch focus.

This patch doesn't really change any semantics but rather clarifies
what was ambiguous before.

Signed-off-by: Jonas Ådahl <jadahl at gmail.com>
---

Changes since v1:

  - Added back the "This is done so that ..." sentence.


 unstable/xdg-shell/xdg-shell-unstable-v6.xml | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/unstable/xdg-shell/xdg-shell-unstable-v6.xml b/unstable/xdg-shell/xdg-shell-unstable-v6.xml
index 1d59a0e..2c8f636 100644
--- a/unstable/xdg-shell/xdg-shell-unstable-v6.xml
+++ b/unstable/xdg-shell/xdg-shell-unstable-v6.xml
@@ -1012,9 +1012,11 @@
 	popup will be immediately dismissed. If the parent is a popup that did
 	not take an explicit grab, an error will be raised.
 
-	Clients will receive events for all their surfaces during this grab
-	(which is an "owner-events" grab in X11 parlance). This is done so that
-	users can navigate through submenus and other "nested" popup windows
+	During a popup grab, the client owning the grab will receive pointer
+	and touch events for all their surfaces as normal (similar to an
+	"owner-events" grab in X11 parlance), while the top most grabbing popup
+	will always have keyboard focus. This is done so that users can
+	navigate through submenus and other "nested" popup windows
 	without having to dismiss the topmost popup.
       </description>
 
-- 
2.7.4