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

[css-device-adaptation] Issues from Kyoto F2F meeting

From: Rune Lillesveen <rune@opera.com>
Date: Tue, 07 Jun 2011 10:28:56 +0200
To: "www-style list" <www-style@w3.org>
Message-ID: <op.vwo5uic48isf1p@id-c1005.oslo.osa>
Hi,

I got an action point from the F2F meeting:


> # [07:01] <fantasai> dbaron: The question is, what does this do on the  
> desktop browser? (And what's a desktop browser)

As far as the spec's concerned, there is no difference. Note that all  
properties are initially 'auto', and without any UA styles, the browser  
will behave as a "desktop" browser.

If you look at the informative section on the viewport meta element,  
you'll see that the current hack in mobile browsers can be modelled as a  
UA stylesheet:

http://dev.w3.org/csswg/css-device-adapt/#ua-stylesheet


> # [07:02] <fantasai> Bert: 2 questions # [07:02] <fantasai> Bert: What's  
> interactions of @viewport and @page

@page is for paged media, @viewport is for continuous media. They don't  
interact.


> # [07:02] <fantasai> Bert: If you put @viewport, can you put @viewport  
> in @media? Say what it means?

It's described in detail with examples:

http://dev.w3.org/csswg/css-device-adapt/#media-queries

The processing model might be too complex. Disallowing @viewport inside  
@media could be done. I don't think that would reduce the functionality  
much.


-- 
Rune Lillesveen
Senior Core Developer / Architect
Opera Software ASA
Received on Tuesday, 7 June 2011 08:29:04 GMT

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