W3C home > Mailing lists > Public > www-style@w3.org > May 2014

Re: why not MediaQueryList.onchange

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 19 May 2014 21:13:48 +0900
Message-ID: <CAAWBYDCKFMJJB8L8JsETP21N=BtjS929nn_odU0d=ChnFpcSsg@mail.gmail.com>
To: Jochen Eisinger <eisinger@google.com>
Cc: www-style list <www-style@w3.org>
On Tue, Apr 1, 2014 at 5:51 AM, Jochen Eisinger <eisinger@google.com> wrote:
> Hey,
> I wonder why MediaQueryList defines its own listener interface
> (MediaQueryListListener) instead of just defining an change event on the
> MediaQueryList itself?
> The reason I ask is because MediaQueryListListener is a pretty unique
> snowflake in the web exposed APIs which makes it very costly to implement
> and somewhat unintuitive to use.

The CSSWG resolved today to do what this thread suggests:

* make MediaQueryList an EventTarget
* fire a non-bubbling "change" event at it whenever things change
* alias the existing addListener(...) to addEventListener("change",
...); same with removeListener()

Received on Monday, 19 May 2014 12:14:36 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:40 UTC