W3C home > Mailing lists > Public > www-style@w3.org > January 2010

Re: Making pt a non-physical unit

From: Brad Kemper <brad.kemper@gmail.com>
Date: Wed, 20 Jan 2010 14:10:13 -0800
Message-Id: <DE7EE9D3-238A-469B-B5DA-71B9104089C2@gmail.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: David Singer <singer@apple.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, "robert@ocallahan.org" <robert@ocallahan.org>, www-style <www-style@w3.org>


On Jan 20, 2010, at 12:48 PM, Giuseppe Bilotta <giuseppe.bilotta@gmail.com 
 > wrote:

>> There may also be times when the UA's choice of zoom level does not  
>> match what the author wants. This could happen in cases where the  
>> content is made especially for the output device but the UA cannot  
>> guess correctly about the resolution of the device or the  
>> appropriate zoom factor to use. For instance, an HTML-based HUD on  
>> sunglasses that are very high resolution, or an overlay for a high  
>> resolution movie that is being projected onto an IMAX screen. Thus,  
>> if there was a property to control that, then the author could use  
>> it, or (for more general Web content) it could be put into a user  
>> style sheet.
>
> In both of these cases, however,  the zoom setting would relative to
> something which is beyond what the designer could forecast (e.g.the
> monitor dpi and the UA default zoom),

Au contraire. I said "in cases where the content is made especially  
for the output device", as opposed to general Web content. So the  
author would know the monitor dpi and UA default zoom choice. Keep in  
mind that CSS is not just for Web pages.

And in the case of user style sheets, these would be used where the  
user did know that the page scaling was always wrong when viewing Web  
pages in his browser. 
    
Received on Wednesday, 20 January 2010 22:11:02 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:23 GMT