Re: why not MediaQueryList.onchange

On Wednesday 2014-04-16 15:21 -0400, Elliott Sprehn wrote:
> lists = copy of mediaLists.
> for each list in lists:
>   eval media query of list.
> for each list in lists:
>   if list is dirty:
>     dispatch change event on list.

I don't think there's any substantive difference in complexity
there; whether the copying is done at the start or inside the first
for loop doesn't really make much difference.

(On the other hand, I don't recall how much complexity it adds to
make something be an EventTarget.  That said, I'm fine with using
events because they fit with the platform [1]; I just think the
complexity argument is not relevant.)


[1] Although I'm not sure to what extent events work well as a
    mechanism for notifications about events internal to the
    platform rather than notifications of changes external to the
    platform.  For example, mutation events didn't work out all that

𝄞   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 19:34:55 UTC