This page is only preserved for historical interest. Current issues for Media Queries are tracked here:
RESOLVED. The draft addresses all of this now. You can use CSS escapes, however.
The syntax for media queries needs some clarification:
Came up in discussion: HTML, CSS, and XML differ in their definition of whitespace. XML has U+0020, U+0009, U+000D, and U+000A. CSS adds U+000C to that list. HTML adds U+000B on top of the CSS list. Is the notion of whitespace languages dependent? @media uses CSS and media=“” uses HTML? (The current proposal seems to be that HTML adds a pre-processing steps that replaces U+000B with U+0020. In that case the notion of whitespace can remain what CSS says.)
Related e-mail thread: http://lists.w3.org/Archives/Public/www-style/2007Nov/thread.html#msg125
What to do with the 'resolution' feature? See e-mail thread: http://lists.w3.org/Archives/Public/www-style/2007Jan/thread.html#msg63 Use cases, what if horizontal and vertical resolution differ, et cetera.
Can you use a media feature with a media type for which it is not applicable? I vote yes. (I being Anne.)
RESOLVED - syntax is now part of the draft.
An idea based on the CSS 2.1 grammar:
media_query_list : S* media_query [ COMMA S* media_query]* ; media_query : [[ONLY | NOT] S+ media_type [S+ AND S+ expression ]*] | expression [ S+ AND S+ expression ]* ; media_type : IDENT ; expression : media_feature [':' S* term]? ; media_feature : IDENT S* ;