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 22:54:58 +0900
Message-ID: <CAAWBYDAGkK=8hF6Vsp2L5FnveXAwpUT1ywzsDi-pm-Fp5KZ_0w@mail.gmail.com>
To: "L. David Baron" <dbaron@dbaron.org>
Cc: Simon Pieters <simonp@opera.com>, Jochen Eisinger <eisinger@google.com>, Fran├žois REMY <francois.remy.dev@outlook.com>, www-style list <www-style@w3.org>
On Mon, May 19, 2014 at 9:55 PM, L. David Baron <dbaron@dbaron.org> wrote:
> On Monday 2014-05-19 21:45 +0900, Simon Pieters wrote:
>> Yes. The wording in the resolution might not include it but we
>> discussed it and my understanding is that we're adding .onchange
>> also.
>
> Are those single-event-listener properties really best practice for
> adding new event types?  They seem rather like footguns, in that
> they break if more than one caller tries to use them (although
> admittedly that's a bit less of a problem for MediaQueryList objects
> since they're likely created by the same caller, at least in their
> current use).
>
> (I don't recall that part of the discussion, though I was searching
> list archives for a bit of it.)

Yes, it's a footgun, but it's also super-convenient and expected by
authors, so we virtually always add them.

~TJ
Received on Monday, 19 May 2014 13:55:46 UTC

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