This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://dev.w3.org/csswg/cssom-view/#dom-mediaquerylist-addlistener [[ addListener ]] <http://www.w3.org/mid/CAPJYB1ia4pj3AaCZVzQx91L=7JPHej-4JrgG8UpE2SEzK-kf2g@mail.gmail.com>
RESOLVED:Make MQ lists and event target for the change event and alias the existing listener to addeventlistener and removeeventlistener http://krijnhoetmer.nl/irc-logs/css/20140519#l-2053
https://dvcs.w3.org/hg/csswg/rev/ce11bd9d0293
Can you please not rely on "When a method or an attribute is said to call another method or attribute, the user agent must invoke its internal API for that attribute or method so that e.g. the author can't change the behavior by overriding attributes or methods with custom properties or functions in ECMAScript." Or at least inline by saying that the UA should use the initial value of those properties. This is a really icky way of writing requirements.
Also, the event is exposed on workers, but is the API itself?
Which properties do you mean? .media and .matched are set to concept-MediaQueryList-media and concept-MediaQueryList-matched. The API isn't exposed to workers currently, but there's a bug asking for that. I guess I can hide the event from workers until then to not confuse feature detection.
The methods are defined as directly invoking addEventListener(). (Also, the rationale for changing this API seems rather sketchy. Making the semantics equivalent to events seems reasonable, but exposing this as events, not so much.)
Thanks https://dvcs.w3.org/hg/csswg/rev/d9c86e52f02a Please reopen or send email to www-style if you care about not exposing the event.