Re: why not MediaQueryList.onchange

On Wednesday 2014-04-09 17:45 -0700, Elliott Sprehn wrote:
> Please do change this to fire a "change" event. The current semantics
> involves a bunch of special logic to deal with copying the handlers and not
> notifying new handlers that are added inside dispatch (across all
> MediaLists which is far different than events). Gecko has that logic too,
> and it's messy.

I don't think we'd get rid of that logic if we switched to events;
we'd still want to fire the events at the end of the internal
processing rather than having to worry about what happens if we call
out to JS in the middle of it.  And that's all it's really doing.

I'm fine with switching to events, though.


𝄞   L. David Baron                  𝄂
𝄢   Mozilla                   𝄂
             Before I built a wall I'd ask to know
             What I was walling in or walling out,
             And to whom I was like to give offense.
               - Robert Frost, Mending Wall (1914)

Received on Wednesday, 16 April 2014 17:11:37 UTC