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

On 1/8/16 1:07 PM, Sebastian Zartner wrote:
> No, it's the same as you implemented in https://bugzil.la/218093. There
> the mouse movement and pointer events are also dispatched on the
> disabled element with it as target, right?

Yes, but they fire the relevant listeners on that element too!  That was 
the whole point: people wanted to get mouse movement events even for the 
disabled elements.

It sounds like you're suggesting a model where the event will fire, and 
build the event propagation chain more or less as normal, but either 
exclude the disabled element from the chain or skip firing listeners on 
it or something.  The question is what the exact proposed behavior is. 
And it would certainly be a change to the guts of core DOM event dispatch.

> I guess that's also what the other browsers do.

That's not consistent with what your previous mail said...

> Taking a JSFiddle[1] for testing I got the following results.

Thanks.  That helps a lot.  Definitely looks like Chrome and IE11 have 
some different event dispatch model.  Edge, on the other hand, is pretty 
close to where Firefox was until my recent changes...

-Boris

Received on Friday, 8 January 2016 19:34:23 UTC