Re: [pointerevents] Should a captured pointer send boundary events by default?

> Here is a short video of the Windows 10 built in "modern" Mail app

that is essentially what I was talking about in the last call (when 
mentioning also how this provides the ability for users to change 
their mind after they started to put their finger on the button, but 
then don't want to execute).

i think it was scott who then said that you wouldn't really do this 
with pointer events and capture, but just listen for click (for the 
action itself, which will only trigger when the end point when the 
finger was lifted is in the same element as where it started). 
probably throw in a `touch-action:none`. but (and i've not tested 
this) i think the actual hover state/highlighting couldn't be achieved
 with pure CSS ... which is why you may need to capture the pointer, 
react to enter/leave to apply/remove some CSS explicitly. i assume 
that the captured pointer would NOT fire a click if its final position
 once pointerup happens is outside of the original element (regardless
 of whether or not it was captured), right?

-- 
GitHub Notification of comment by patrickhlauke
Please view or discuss this issue at 
https://github.com/w3c/pointerevents/issues/61#issuecomment-220195155 
using your GitHub account

Received on Thursday, 19 May 2016 00:16:51 UTC