[PATCH inputproto] specs: Clarify rejection for touch events on current owner

[Peter Hutterer]

The current owner never gets a TouchUpdate(PendingEnd), that event is
superfluous for the owner. The owner receives a TouchEnd when the touch
physically ends. If the touch is still active, the owner receives a
TouchEnd after rejecting the touch.

Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>
---
This is the current server behaviour, the spec was wrong.

Note that this section needs rearranging, ownership is described a bit
out-of-order and possibly hard to understand if you don't already know what
it is. Will do that in a later patch.

 specs/XI2proto.txt |   15 ++++++++++-----
 1 files changed, 10 insertions(+), 5 deletions(-)

diff --git a/specs/XI2proto.txt b/specs/XI2proto.txt
index 0455ed3..2f03b50 100644
--- a/specs/XI2proto.txt
+++ b/specs/XI2proto.txt
@@ -366,11 +366,16 @@ TouchEnd events, and the touch sequence is exclusively delivered to the
 owner from that point on.
 
 If the touch sequence physically ends while the owner of the touch sequence
-has not yet accepted or rejected ownership, all clients receive a
-TouchUpdate event with the TouchPendingEnd flag set. The owner must still
-accept or reject the sequence nonetheless. If the owner rejects the touch
-sequence, the server will still attempt to exhaust all other passive grabs
-and/or event selections looking for a final owner.
+has not yet accepted or rejected ownership, the owner receives a TouchEnd
+event and all other clients receive a TouchUpdate event with the
+TouchPendingEnd flag set. The owner must still accept or reject the sequence
+nonetheless. If the owner rejects the touch sequence, the server will still
+attempt to exhaust all other passive grabs and/or event selections looking
+for a final owner.
+
+If the touch sequence has not physically ended yet and the owner of the
+touch sequence rejects, the owner receives a TouchEnd event and ownership is
+passed to the next client.
 
 Clients may opt for touch events to be delivered before they become the
 owner of the touch sequence. In this case, the logical state of the device (as
-- 
1.7.7.4