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

Re: [css3-mediaqueries] Application to @media and @import rules.

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Tue, 17 Jun 2008 01:03:29 +0200
To: fantasai <fantasai.lists@inkedblade.net>
Cc: www-style@w3.org
Message-ID: <hkrd541k1naab7annnve4ccvu05j7teegm@hive.bjoern.hoehrmann.de>

* fantasai wrote:
>   # If the comma-separated list is the empty list it is assumed to specify the
>   # media query ‘all’.
>
>Currently @media { ... } is invalid in CSS2.1. I think it should therefore remain
>invalid in CSS Level 3, and in that case you will need wording somewhere that the
>media list in @media rules cannot be empty.

That needs to be specified in the specification for the @media rule,
unless you are asking that the empty list should be invalid everywhere.

>   # The media queries syntax can be used with HTML, XHTML, XML [XMLSTYLE] and the
>   # @import and @media rules of CSS.
>
>This sentence is very imprecise. If you're going to say something normative about
>these technologies, then you should specify precisely how media queries syntax can
>be used and cite the specifications that define the technologies you're modifying.
>For example, you can say that media queries replaces the 'media' attribute syntax
>in HTML4 and the XHTML languages based off of that spec. Later versions of these
>technologies can then cite Media Queries directly, e.g. HTML5 can refer to Media
>Queries.

In response to disagreement between myself and the HTML Working Group,
the Hypertext Coordination Group decided how the divergent types and
syntaces for media attributes and similar contexts should be handled.

I do not believe the above is meant to make normative changes to these
other specifications, and I do not think it should do so, so a better
change would be to say, it is expected that the relevant specifications
will be updated to enable use of media queries as in these examples.

I would very much dislike a situation where specifications modify each
other with no clear process for that, and no clear index to check for
any such updates. The IETF has this in place, the W3C not at all.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Monday, 16 June 2008 23:04:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:07 GMT