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:46:09 +0900
Message-ID: <CAAWBYDAti9x6QKG+z=i5b=_3Vidw215S+Ghp3Q+kp6w2SS8a0g@mail.gmail.com>
To: François REMY <francois.remy.dev@outlook.com>
Cc: Jochen Eisinger <eisinger@google.com>, www-style list <www-style@w3.org>
On Mon, May 19, 2014 at 9:39 PM, François REMY
<francois.remy.dev@outlook.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()
>
> Does it include the "mq.onchange" property?

Yeah, it will.

~TJ
Received on Monday, 19 May 2014 12:46:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:51:27 UTC