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

Re: why not MediaQueryList.onchange

From: Simon Pieters <simonp@opera.com>
Date: Sat, 09 Aug 2014 21:56:43 +0200
To: "Jonathan Fielding" <hello@jonathanfielding.com>, "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: "Jochen Eisinger" <eisinger@google.com>, "www-style list" <www-style@w3.org>
Message-ID: <op.xkccctmvidj3kv@simons-mbp>
On Fri, 08 Aug 2014 19:45:36 +0200, Tab Atkins Jr. <jackalmage@gmail.com>  

> On Fri, Aug 8, 2014 at 10:36 AM, Jonathan Fielding
> <hello@jonathanfielding.com> wrote:
>> By baking this right into the browser, the browser controls the  
>> performance
>> optimisation, so in the case of a resize event only for large  
>> viewports, on
>> smaller viewports we won’t have any resize methods firing.

I'm not convinced it would make any difference in performance.

> This seems like a bit of a layering violation.  Why would 'resize'
> events be the only thing you'd want to apply this kind of filtering
> to?  I can easily see arguments for practically any event being
> limited by an MQ test.
> You can do this yourself quite easily, by adding the listener on match
> and removing it on unmatch, using code nearly identical to what you
> posted in your previous message.  This gives you the flexibility to
> use any event, on any object, using any arbitrary additional
> constraints you wish.


Simon Pieters
Opera Software
Received on Saturday, 9 August 2014 19:57:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:24 UTC