- From: smaug---- via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Mar 2017 15:47:44 +0000
- To: public-pointer-events@w3.org
smaug---- has just created a new issue for https://github.com/w3c/pointerevents: == The spec is unclear whether boundary events should fire while pointer is captured to a certain target == setPointerCapture says: "For subsequent events of the pointer, the capturing target will substitute the normal hit testing result as if the pointer is always over the capturing target" pointerleave (as an example): "A user agent MUST fire a pointer event named pointerleave when a pointing device is moved out of the hit test boundaries of an element and all of its descendants, including as a result of a pointerup and pointercancel events from a device that does not support hover (see pointerup and pointercancel). Note that setPointerCapture or releasePointerCapture might have changed the hit test target." So, if pointer is moved outside the capturing target, per spec pointerleave should fire, since, well pointing device is outside hit test boundaries (note, moving outside the boundaries doesn't necessarily mean hit testing). But then setPointerCapture says hit testing doesn't happen and I guess it tries to say pointerleave shouldn't be dispatched. Could this be clarified? Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/185 using your GitHub account
Received on Tuesday, 7 March 2017 15:47:50 UTC