Re: [css3-mediaqueries] tv and screen media types

On Fri, 29 Oct 2010 12:30:10 +0200, David Storey <dstorey@opera.com> wrote:

>
> On 29 Oct 2010, at 09:45, Rune Lillesveen wrote:
>
>> On Fri, 29 Oct 2010 09:14:31 +0200, fantasai  
>> <fantasai.lists@inkedblade.net> wrote:
>>
>>> On 10/28/2010 05:41 AM, Rune Lillesveen wrote:

>>>> Pumping up the pixel size of a font based on physical DPI is only  
>>>> needed
>>>> for broken UAs, right? See [1]
>>>>
>>>> [1] http://www.w3.org/TR/CSS21/syndata.html#pixel-units
>>>
>>> Note that definition of the pixel has been superseded.
>>> http://fantasai.inkedblade.net/style/specs/css2.1/px-unit
>>> http://csswg.inkedblade.net/spec/css2.1#issue-149
>>
>> Yes, and with that definition, for tv, the physical units would be  
>> anchored to the reference pixel, making it even less interesting to  
>> change font-sizes based on the resolution media feature.
>
> Yes, as far as I see it, browsing on TV is a different context. It is  
> less about DPI and resolution, and more about the context you are  
> viewing web pages. Usually in a more social setting. PC and mobile is  
> more one to one where you are close to the screen, while with TV you are  
> about 10 feet away, and often (but not always) i a more social setting  
> where multiple people can see the content. For this you don’t care about  
> the DPI, but more that the user is viewing on a TV (TV media type) and  
> you want to adjust the layout; The most simple being the text size so it  
> is physically big enough to read across the room instead of readable at  
> a few cm from the screen.

That's exactly the point of the reference pixel being defined by a visual  
angle and not resolution. The UA should adjust the CSS pixel size, and  
hence other sizes using the new definition. The author should not need to  
care.

-- 
Rune Lillesveen
Senior Core Developer / Architect
Opera Software ASA

Received on Friday, 29 October 2010 10:51:21 UTC