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: 
[Mail App Video](https://1drv.ms/v/s!AjqY3A8n3XjcrfMMltLo7R5kzGSvZg) 
Notice how the pointer gets captured to the button that the is first 
touched, then no other buttons or anywhere else on the screen is 
getting pointer events. When the finger is returned to the original 
button and released, then the action for the button is completed. This
 is the button concept that we are trying to replicate on the web and 
why we need pointerenter and pointerleave events on the element that 
has captured the pointer.

Another example, although contrived and clearly not something that a 
designer would ever sign off on, can be seen here: 
[http://teddin.azurewebsites.net/test/pointereventbutton.html](http://teddin.azurewebsites.net/test/pointereventbutton.html)
 Pointerdown in the yellow div captures the pointer and changes the 
color and border. When the user moves outside that border, the div 
changes back to yellow, while the border remains to indicate that the 
div has capture. While captured by the bordered div, the green div 
never receives the pointerover events it is listening for. Moving back
 to the yellow bordered div, turns it blue again to indicate that the 
pointer could now complete the action that would be associated with 
the "button".

Does this better explain the button scenario referenced above?

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

Received on Wednesday, 18 May 2016 23:57:06 UTC