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

Re: Making pt a non-physical unit

From: David Singer <singer@apple.com>
Date: Thu, 21 Jan 2010 09:21:23 +0900
Cc: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, "robert@ocallahan.org" <robert@ocallahan.org>, www-style <www-style@w3.org>
Message-Id: <018B4BF1-451A-4A1F-8AE3-55DB77E5B8BF@apple.com>
To: Brad Kemper <brad.kemper@gmail.com>
If I am designing for a specific device, I can know its characteristics and default settings, and do the scaling myself.  Why do we need something in a spec. that is covering the 'arbitrary interoperability' problem.

On Jan 21, 2010, at 7:10 , Brad Kemper wrote:

> 
> 
> 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.  

David Singer
Multimedia and Software Standards, Apple Inc.
Received on Thursday, 21 January 2010 00:21:58 GMT

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