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

Re: [mediaqueries] Media Source Extensions and device capabilities

From: Florian Rivoal <florian@rivoal.net>
Date: Tue, 18 Nov 2014 14:59:23 +0100
Cc: Mark Watson <watsonm@netflix.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, "www-style@w3.org" <www-style@w3.org>
Message-Id: <F1A7F56B-AEB1-4913-9E43-51CB434DC566@rivoal.net>
To: "L. David Baron" <dbaron@dbaron.org>

> On 14 Nov 2014, at 18:13, L. David Baron <dbaron@dbaron.org> wrote:
> I could certainly imagine the group being less concerned about
> device pixels being used as a unit in media queries if the media
> query were a (media-width) query that queried against the size of
> the HTML media element and were specific to media selection, rather
> than a (width) query that queries against the size of the viewport?
> Or is there an infinite loop there in that the size of the media
> element might be determined by the resource selection?

There is, since you’d be be able to resize the video element in a media query triggered by the size of the video element. If we really wanted it, we can of course insert some explicit rule to break the loop, but this design doesn’t feel particularly clean to me.

> Then again, I probably wouldn't be against just having a separate
> unit for device pixels (or, for that matter, for true lengths),
> although I'm not sure I like 'dpx' as the name (looks too much like
> 'dpi’).

We already have dppx (Dots Per PiXels) for the resolution MQ, to query the number of physical pixels in a css pixels, so I don’t think dpx is a name I’d recommend.

As for physical units for lengths, coming from mostly anyone else, I’d probably reply with the usual story about why this is misguided, but as you know all these already, I am curious as to why you think this is a potentially good idea.

 - Florian
Received on Tuesday, 18 November 2014 13:59:48 UTC

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