Re: UNS: [Moderator Action] Re: [css-device-adaptation] Progress?

> On 28 Apr 2015, at 03:35, GPMCGINN@aol.com wrote:
> 
> I am currently "fighting" to find a simple way to make Google Mobile like my sites pages. I strive to have all HTML 5 pages have no errors and just one CSS file to control all.
>  
> It seems like the CSS verifier currently doesn't support @viewport although some of my test pages seem to actually function on the web as intended.
>  
> I would like @viewport usage within an @media usage near the top of a CSS file. This seems natural to me to control mobile device viewport, perhaps even multiple ones, at the highest level and in one place vs within multiple HTML files. 
>  
> One of the recent comments, 26 Feb 2015, says:
>  
> " All in all, I see that there's a valid use case for permitting @viewport
> rules in external styles other than mere convenience.
> So, perhaps limiting @viewport rules to be one of the first rules in an
> external style (along with @charset and @import) would be enough, if
> coupled with user agent scanning those files to extract these rules, along
> with console warnings of possible performance issues.
> 
> Rune, Florian - WDYT?"


@viewport is already allowed inside an @media, and how media queries (either in @media, on an @import, in a link element...) interact with it is also defined.

It is not allowed before @import, and based on the recent discussions, that is unlikely to change.

However, this doesn't mean that the media condition on an @import cannot take into account the @viewport, only that the preloader won't pick it up, so there may be a change in how it's evaluated later on when the full engine kicks in.

 - Florian