RE: pointerdown/pointerup on non-hover devices

Yes, an editorial mistake when we added enter/leave. Fixed in the latest editor’s draft [1]. Great catch, thanks!



On Tue, Jan 21, 2014 at 3:55 PM, Rick Byers <<>> wrote:
Hah, good catch.  We added pointerenter/pointerleave late in the process - probably just missed referencing it in a few places.  Note that the description of pointerenter/pointerleave do say this is required, eg 5.2.8 pointerenter:
"A user agent must dispatch this event when a pointing device is moved into the hit test boundaries of an element or one of its descendants, including as a result of a pointerdown event from a device that does not support hover."

Want to file a bug for Jacob to update sections 5.2.2 and 5.2.3 to reference pointerenter/pointerleave?  I don't see any other place this is missing, do you?


On Tue, Jan 21, 2014 at 6:45 PM, Patrick H. Lauke <<>> wrote:
In the current spec, pointerdown/pointerup/pointercancel on input devices that do not support hover MUST fire a pointerover/pointerout/pointerout (respectively, before in the first case and after in the other two cases). But why not also a pointerenter/pointerleave?

Patrick H. Lauke
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]<> |<><> |

twitter: @patrick_h_lauke | skype: patrick_h_lauke

Received on Wednesday, 22 January 2014 22:54:11 UTC