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

Re: why not MediaQueryList.onchange

From: Simon Pieters <simonp@opera.com>
Date: Mon, 19 May 2014 22:13:49 +0900
To: "L. David Baron" <dbaron@dbaron.org>
Cc: "'Tab Atkins Jr.'" <jackalmage@gmail.com>, "'Jochen Eisinger'" <eisinger@google.com>, Fran├žois REMY <francois.remy.dev@outlook.com>, "'www-style list'" <www-style@w3.org>
Message-ID: <op.xf3y1bfxidj3kv@simons-macbook-pro.local>
On Mon, 19 May 2014 21:55:28 +0900, 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're basically always added. They are also convenient in simple cases.

> 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).

Right.

> (I don't recall that part of the discussion, though I was searching
> list archives for a bit of it.)

http://krijnhoetmer.nl/irc-logs/css/20140519#l-2025

Maybe it was more mentioned in passing than actually discussed.

-- 
Simon Pieters
Opera Software
Received on Monday, 19 May 2014 13:14:41 UTC

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