W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2007

Re: Accept- & Content-Resolution headers proposal

From: Stewart Brodie <stewart.brodie@antplc.com>
Date: Thu, 7 Jun 2007 18:18:43 +0100
To: Travis Snoozy <ai2097@users.sourceforge.net>
Cc: Nicholas Shanks <contact@nickshanks.com>, ietf-http-wg@w3.org
Message-ID: <aa8cea881300c7ef8ae0ff32198a2c2d5df09de9@localhost>

Travis Snoozy <ai2097@users.sourceforge.net> wrote:

> I'm betting that CSS doesn't have anything to switch on DPI yet. As a
> totally fictional example:
> 
> @media screen.300dpi {
> @import url('/300dpi.css');
> }
> 
> @media print.1200dpi {
> @import url('/1200dpi.css');
> }
> 
> Syntax, of course, would be up to negotiation, but this provides a
> general idea. The DPI switching should be done in CSS.

It can.  CSS Media Query:  http://www.w3.org/TR/css3-mediaqueries/

@media screen and (resolution: 300dpi) { @import url(/300dpi.css); }
@media screen and (resolution: 1200dpi) { @import url(/1200dpi.css);}

Where appropriate, media query keywords can take an optional min- or max-
prefix to convert the equality comparison into a greater than or equal, or
less than or equal.  e.g.

@media screen and (min-resolution: 1200dpi) { @import url(/1200+dpi.css); }


-- 
Stewart Brodie
Software Engineer
ANT Software Limited
Received on Thursday, 7 June 2007 17:20:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:10 GMT