- From: Scott González via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Jun 2016 00:20:51 +0000
- To: public-pointer-events@w3.org
Only scenario 2 was unexpected to me. The relative order of `pointerup` and `lostpointercapture` is defined in the spec, but the relative order of `lostpointercapture` and `click` is undefined, so I'm inclined to ignore the fact that this specific implementation fires `lostpointercapture` after `click`. With that in mind, here's why only scenario 2 was unexpected: A click occurs when a button is pressed and released on the same element. Because pressing either the green or blue element inherently means pressing the grey element, I expect the grey element to receive a click in all scenarios. Only the first scenario should have a *target* other than grey, because a descendant of grey was the target of both the press and release. There were also comments about this yesterday starting at https://github.com/w3c/pointerevents/issues/61#issuecomment-223019912. -- GitHub Notification of comment by scottgonzalez Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/75#issuecomment-223460061 using your GitHub account
Received on Friday, 3 June 2016 00:20:53 UTC