


From: Brad Kemper <brad.kemper@gmail.com>
Date: Wed, 26 Oct 2011 15:02:06 -0700
Message-Id: <3D2F4D51-4564-4C38-84CA-A1D161BBB2AD@gmail.com>
Cc: Boris Zbarsky <bzbarsky@MIT.EDU>, Brian Blakely <anewpage.media@gmail.com>, "<www-style@w3.org>" <www-style@w3.org>
To: François REMY <fremycompany_pub@yahoo.fr>
On Oct 26, 2011, at 2:45 PM, François REMY <fremycompany_pub@yahoo.fr> wrote:

> Are you basicly saying that since no solution is perfect we should have no solution to the problem at all?
> To me, it seems like the physical size of a device is (nearly) sufficient enough to adapt your design (Input/Output methods available should be taken in consideration too). If you want to challenge that idea, feel free, but come up with cases where having physical measurements of the device is a bad thing or don't help to solve a layout choice problem.

One JumboTron-like display is 640x480 (using lightbulbs), and another is 1600x1200 (using LEDs). If you want to display a Web page on both, using media queries on pixels is going to be much more useful than knowing their physical size. Same thing for projectors, where the actual physical pixels might be on something the size of a postage stamp (or smaller), but it is often unknowable how far away the screen is (and thus how big the final projection is on that screen). What happens in these cases when you write a media query for your Web page about the physical size?

Received on Wednesday, 26 October 2011 22:02:42 GMT
