[pointerevents] Should spec defines what triggers pointerover and pointerenter when implicitly releasing pointer capture?

mingchou has just created a new issue for 
https://github.com/w3c/pointerevents:

== Should spec defines what triggers pointerover and pointerenter when
 implicitly releasing pointer capture? ==
I knew this had been discussed in #145, but I'm still not sure about 
what triggers pointerover and pointerenter when implicit releasing 
pointer capture.

When the pointer is captured, hit test target is the pointer capture 
target override object. That means UA won't run the normal hit test 
algorithm. When implicitly releasing pointer capture, the hit test 
target is changed, and UA must fire boundary events. Should spec 
define what triggers UA run the normal hit test algorithm to determine
 the hit test target and fire pointerover / pointerenter to it?

e.g. When the pointer is captured by element A while pointer is 
hovering on element B, pointer is implicitly released when pointerup. 
What trigger UA to run the hit test algorithm and fire pointerover / 
pointerenter to B (in the case of the pointer isn't moved) ?

Tested on Chrome, boundary events are fired with a pointermove event. 
Edge fires boundary events with the subsequent pointermove event 
(happened when the pointer is moved).

Please view or discuss this issue at 
https://github.com/w3c/pointerevents/issues/173 using your GitHub 
account

Received on Monday, 23 January 2017 14:56:51 UTC