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

Re: [CSS21] Issue 149 - px vs. pt

From: fantasai <fantasai.lists@inkedblade.net>
Date: Wed, 30 Jun 2010 12:06:34 -0700
Message-ID: <4C2B95BA.1090208@inkedblade.net>
To: Sylvain Galineau <sylvaing@microsoft.com>
CC: "robert@ocallahan.org" <robert@ocallahan.org>, "www-style@w3.org" <www-style@w3.org>
On 06/30/2010 10:17 AM, Sylvain Galineau wrote:
>> From: fantasai [mailto:fantasai.lists@inkedblade.net]
>> Sent: Wednesday, June 30, 2010 10:09 AM
>> To: Sylvain Galineau
>> Cc: robert@ocallahan.org; www-style@w3.org
>> Subject: Re: [CSS21] Issue 149 - px vs. pt
>> Right. If I'm designing a touch UI, which is one of the use cases
>> that Mozilla is concerned with, I'd want real dimensions, not the
>> size of some imaginary canvas. Not being able to get those
>> dimensions even through media queries, which were specifically
>> designed to do this, would be a very frustrating problem.
> If we're talking about XUL running on a phone, sure. But the web
> page rendered by the browser may still not get the physical viewport
> size. In practice context will be provide a switch i.e. if you're writing
> a web app that runs offline and launches from its own icon on a device, you
> want and will get a physical viewport size. If it's a web page, you may never
> know because the browser can lie to you.

That's a horrible way to treat web apps that aren't yet
important enough to you to run offline. How can you
possibly provide the user with a reasonable experience
if a 2in screen tells you that it's 22in wide?

Received on Wednesday, 30 June 2010 19:07:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:47 UTC