- From: Rick Byers <rbyers@google.com>
- Date: Tue, 21 Jan 2014 18:55:13 -0500
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- Cc: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
- Message-ID: <CAFUtAY9UU27H4YV6pBEZrnXcoBLR9Jrynq+Y9SGk75K-X2dBAg@mail.gmail.com>
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? Rick On Tue, Jan 21, 2014 at 6:45 PM, Patrick H. Lauke <redux@splintered.co.uk>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? > > P > -- > Patrick H. Lauke > ______________________________________________________________ > re·dux (adj.): brought back; returned. used postpositively > [latin : re-, re- + dux, leader; see duke.] > > www.splintered.co.uk | www.photographia.co.uk > http://redux.deviantart.com | http://flickr.com/photos/redux/ > ______________________________________________________________ > twitter: @patrick_h_lauke | skype: patrick_h_lauke > ______________________________________________________________ > >
Received on Tuesday, 21 January 2014 23:56:06 UTC