W3C home > Mailing lists > Public > public-html@w3.org > January 2016

Re: Should mouse events be triggered on ancestors of disabled elements?

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Mon, 4 Jan 2016 03:10:27 -0500
To: public-html@w3.org
Message-ID: <568A28F3.1040207@mit.edu>
On 1/3/16 12:05 PM, Sebastian Zartner wrote:
> The event is dispatched on the disabled form element with the disabled
> form element as target.

OK.  So we're talking about a fundamental change to the core DOM event 
dispatch algorithm here, right?

> Firefox only triggers mousemove, mouseover and mouseout events.

And mouseenter, mouseleave, and the equivalent pointer events.  Further, 
Firefox triggers event listeners for those on all the elements involved, 
including the disabled form control, not just on ancestors right?

As in, Firefox doesn't change the core DOM event dispatch algorithm; it 
simply doesn't fire some events in some cases in which one might expect 
them to fire.

> Chrome and Opera trigger all events except mouseenter and mouseleave,
> though not on <button>, <input type="radio"> and <input
> type="checkbox"> elements.
> Internet Explorer triggers all events.
> Edge triggers no events at all. (looks like this has changed since my last mail)

Given the inaccurate description of the Firefox behavior above, I'd 
really like to understand precisely what the behaviors of those browsers 
actually are...

Received on Monday, 4 January 2016 08:10:57 UTC

This archive was generated by hypermail 2.3.1 : Monday, 4 January 2016 08:10:57 UTC