- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 May 2016 18:06:34 +0000
- To: public-pointer-events@w3.org
On [the call] it seemed this issue was largely blocked on the big fundamental question of what the right model for transition events during capture is. Filed #61 to try to get consensus on that. If we want to move forward in parallel with that, it seems there was agreement that: 1. Firing transition events at one element after a new one has received `gotpointercapture` is a bug * Step 20 and 21 should occur before 19 (and possibly before 18) [above](https://github.com/w3c/pointerevents/issues/39#issue-139363428) 2. The spec should indicate that `pointerover` and `pointerout` behave the same as `pointerenter` and `pointerleave` during capture in that they reflect the bounds of the captured element and all it's descendants. -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/39#issuecomment-216951227 using your GitHub account
Received on Wednesday, 4 May 2016 18:06:36 UTC