- From: Jacob Rossi <Jacob.Rossi@microsoft.com>
- Date: Tue, 20 Nov 2012 23:57:14 +0000
- To: Rick Byers <rbyers@google.com>, "olli@pettay.fi" <olli@pettay.fi>
- CC: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
I agree that mouseenter/mouseleave should not be required if a UA doesn't implement them. In fact, neither should mousedown/mouseup/mousemove/mouseover/mouseout. I consider the section on mouse events purely for compat with legacy content. You could imagine a UA that doesn't have legacy content to deal with and just wants to implement pointer. Once we have an issue tracker, we should add this. Though, for browsers, I agree with Olli: mouseenter/mouseleave are great. I'd like to discuss adding pointerenter/pointerleave as well (also should be added to issue tracker). The primary reason these are good events is that they map to the CSS :hover state. -Jacob -----Original Message----- From: Rick Byers [mailto:rbyers@google.com] Sent: Wednesday, November 21, 2012 5:40 AM To: olli@pettay.fi Cc: public-pointer-events@w3.org Subject: Re: Make mouseenter/mouseleave behavior optional On Tue, Nov 20, 2012 at 1:58 PM, Olli Pettay <Olli.Pettay@helsinki.fi> wrote: > On 11/20/2012 08:23 PM, Rick Byers wrote: >> >> Hi, >> In the compatibility with mouse events section [1], the pointer >> events draft dictates when mouseenter and mouseleave events should be >> dispatched. However, I believe today only IE and Opera support these >> events [2]. > > Only webkit does not support mouseenter and mouseleave, and IIRC Ah yes, I see the quirksmode page is wrong - Firefox does too. > there are some patches even for webkit to support them. > > > Can we add an 'if supported by the UA' to the wording to >> >> make it clear that some UAs won't dispatch these events? > > Why? mouseenter/leave are spec'ed elsewhere and implementations should > support them. > I guess it's not a big deal. I just wouldn't want to imply that a complete implementation of pointer events MUST support mouseenter/mouseleave also - it would make it harder to get such an implementation into WebKit. If mouseenter/mouseleave is really the right way forward, then I'd argue we should have pointerenter/pointerleave too.
Received on Tuesday, 20 November 2012 23:58:22 UTC