W3C home > Mailing lists > Public > public-pointer-events@w3.org > January to March 2016

Re: [pointerevents] Incorrect order of the events in process pending pointer capture section

From: Rick Byers via GitHub <sysbot+gh@w3.org>
Date: Tue, 08 Mar 2016 20:05:41 +0000
To: public-pointer-events@w3.org
Message-ID: <issue_comment.created-193946090-1457467540-sysbot+gh@w3.org>
> Problem 1. Current spec wording misses the firing of out/leave 
events when the capturing directly "moves" from one element to 
another. Edge fires the events in a logical manner, not following the 
spec (from step 5 to end)

I agree we should just fix this in the spec.

> Problem 2'. Before "blue" receives pointermove in step 22, it should
 receive pointerover/enter. Spec is silent again as in Problem 1, but 
Edge follows the spec this time.

Why do you say blue should receive pointerover/enter?  Even when 
captured, I thought an element should get over/enter only when the 
cursor has crossed into the bounds of the element.

> Problem 3. After "blue" captures the pointer (step 19), "green" 
shouldn't receive any event. So firing of pointerout/leave to "green" 
(steps 20, 21) is conceptually wrong even though the spec suggests the
 same order if "green" hadn't captured the mouse in step 5. Edge 
implementation seems to follow the spec order.

I agree that seems more logical.  The implications in practice aren't 
clear to me though - are there scenarios that would work better or 
worse given this change?



-- 
GitHub Notification of comment by RByers
Please view or discuss this issue at 
https://github.com/w3c/pointerevents/issues/39#issuecomment-193946090 
using your GitHub account
Received on Tuesday, 8 March 2016 20:05:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 8 March 2016 20:05:53 UTC