css3-conditional/Overview.src.html

Thu, 15 Nov 2012 11:52:08 -0800

author
fantasai <fantasai.cvs@inkedblade.net>
date
Thu, 15 Nov 2012 11:52:08 -0800
changeset 7042
fe8bd7278569
parent 7038
5c72ce286bf3
child 7043
76586af82d2d
permissions
-rw-r--r--

[css3-conditional] Prep draft for lcwd

     1 <!DOCTYPE html public '-//W3C//DTD HTML 4.01//EN'
     2   'http://www.w3.org/TR/html4/strict.dtd'>
     3 <html lang="en">
     4 <head profile="http://www.w3.org/2006/03/hcard">
     5   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
     6   <title>CSS Conditional Rules Module Level 3</title>
     7   <link rel="stylesheet" type="text/css" href="../default.css">
     8   <link rel="stylesheet" type="text/css"
     9         href="http://www.w3.org/StyleSheets/TR/W3C-[STATUS].css">
    10 <!--
    11   <script src="http://test.csswg.org/harness/annotate.js#CSS3-CONDITIONAL_DEV" 
    12         type="text/javascript" defer></script
    13 -->
    14 </head>
    16 <div class="head">
    17 <!--logo-->
    19 <h1>CSS Conditional Rules Module Level 3</h1>
    21 <h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
    22 <dl>
    23   <dt>This version:
    24     <dd><a href="[VERSION]">
    25     http://www.w3.org/TR/[YEAR]/WD-css3-conditional-[CDATE]/</a>
    27   <dt>Latest version:
    28     <dd><a href="http://www.w3.org/TR/[SHORTNAME]/">http://www.w3.org/TR/[SHORTNAME]/</a>
    30   <dt>Editor's draft:
    31     <dd><a href="http://dev.w3.org/csswg/[SHORTNAME]/">http://dev.w3.org/csswg/[SHORTNAME]/</a>
    33   <dt>Previous version:
    34     <dd><a href="http://www.w3.org/TR/2012/WD-css3-conditional-20120911/">http://www.w3.org/TR/2012/WD-css3-conditional-20120911/</a></dd>
    36   <dt>Editors:
    37     <dd class=vcard><a class=fn href="http://dbaron.org/">L. David Baron</a>,
    38       <a class=org href="http://www.mozilla.org/">Mozilla</a>
    40   <dt>Issues list:
    41     <dd>Maintained in document (only editor's draft is current)
    43     <dt>Feedback:
    45     <dd><a
    46      href="http://lists.w3.org/Archives/Public/www-style/">www-style@w3.org</a>
    47      with subject line “<kbd>&#x5b;[SHORTNAME]&#x5d; <var>… message topic
    48      …</var></kbd>”
    50   <dt>Test suite:
    51     <dd><a href="https://test.csswg.org/shepherd/search/spec/css3-conditional/">submitted tests</a>; no built test suite yet
    53 </dl>
    55 <!--copyright-->
    57 <hr title="Separator for header">
    58 </div>
    60 <h2 class="no-num no-toc" id="abstract">Abstract</h2>
    62   <p>CSS is a language for describing the rendering of structured documents
    63   (such as HTML and XML) on screen, on paper,  in speech, etc. This module
    64   contains the features of CSS for conditional processing of parts of
    65   style sheets, conditioned on capabilities of the processor or the
    66   document the style sheet is being applied to.
    67   It includes and extends the functionality of CSS level&nbsp;2 [[!CSS21]],
    68   which builds on CSS level&nbsp;1 [[CSS1]].
    69   The main extensions compared to level&nbsp;2 are
    70   allowing nesting of certain at-rules inside '@media',
    71   and the addition of the '@supports'
    72   rule for conditional processing.
    74 <h2 class="no-num no-toc" id="status">Status of this document</h2>
    76 <!--status-->
    78 <p>The following features are at risk:
    79 <ul>
    80   <li>The inclusion of '@font-face' rules and
    81   '@keyframes' rules as allowed within all of the @-rules in
    82   this specification is at risk, though only because of the relative
    83   rates of advancement of specifications.  If this specification is able
    84   to advance faster than one or both of the specifications defining
    85   those rules, then the inclusion of those rules will move from this
    86   specification to the specification defining those rules.</li>
    88   <li>The addition of support for @-rules inside of conditional grouping
    89   rules is at risk; if interoperable implementations are not found, it
    90   may be removed to advance the other features in this specification to
    91   Proposed Recommendation.</li>
    93   <li>The '@supports' rule is at risk; if interoperable
    94   implementations are not found, it may be removed to advance the other
    95   features in this specification to Proposed Recommendation.</li>
    96 </ul>
    98 <p>This is a <strong>Last Call Working Draft</strong>.
    99 The deadline for comments is <strong>18 December 2012</strong>.
   101 <!--
   103   Things to go in level 4:
   105   * Create some way to put these new conditional things on an @import.
   106   * The @document rule (commented out, down below).
   108 -->
   110 <h2 class="no-num no-toc" id="contents">Table of contents</h2>
   112 <!--toc-->
   114 <h2 id="introduction">Introduction</h2>
   116 <h3 id="context">Background</h3>
   118   <p><em>This section is not normative.</em>
   120   <p>[[!CSS21]] defines one type of conditional group rule, the
   121   '@media' rule, and allows only rulesets (not other @-rules)
   122   inside of it.  The '@media' rule provides the ability to
   123   have media-specific style sheets, which is also provided by style
   124   sheet linking features such as '@import' and
   125   <code class="html">&lt;link&gt;</code>.  The restrictions on the contents of
   126   '@media' rules made them less useful; they have forced authors
   127   using CSS features involving @-rules in media-specific style sheets to
   128   use separate style sheets for each medium.</p>
   130   <p>This specification extends the rules for the contents of
   131   conditional group rules to allow other @-rules, which enables authors
   132   to combine CSS features involving @-rules with media specific style
   133   sheets within a single style sheet.</p>
   135   <p>This specification also defines an additional type of conditional
   136   group rule, '@supports', to
   137   address author and user requirements.</p>
   139   <p>The '@supports' rule allows CSS to be conditioned on
   140   implementation support for CSS properties and values.  This rule makes
   141   it much easier for authors to use new CSS features and provide good
   142   fallback for implementations that do not support those features.  This
   143   is particularly important for CSS features that provide new layout
   144   mechanisms, and for other cases where a set of related styles needs to
   145   be conditioned on property support.</p>
   147 <h3 id="placement">Module Interactions</h3>
   149   <p>This module replaces and extends the '@media' rule
   150   feature defined in [[!CSS21]] section <var>7.2.1</var> and
   151   incorporates the modifications previously made non-normatively by
   152   [[!MEDIAQ]] section <var>1</var>.</p>
   154   <p>Its current definition depends on @-rules defined in [[!CSS3-FONTS]]
   155   and [[!CSS3-ANIMATIONS]], but that dependency is only on the
   156   assumption that those modules will advance ahead of this one.  If this
   157   module advances faster, then the dependency will be reversed.</p>
   159 <h3 id="conventions">Document Conventions</h3>
   161   <p>Conformance requirements are expressed with a combination of
   162   descriptive assertions and RFC 2119 terminology. The key words “MUST”,
   163   “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
   164   “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
   165   document are to be interpreted as described in RFC 2119.
   166   However, for readability, these words do not appear in all uppercase
   167   letters in this specification.
   169   <p>All of the text of this specification is normative except sections
   170   explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>
   172   <p>Examples in this specification are introduced with the words “for example”
   173   or are set apart from the normative text with
   174   <code class="html">class="example"</code>, like this:
   176   <div class="example">
   177     <p>This is an example of an informative example.</p>
   178   </div>
   180   <p>Informative notes begin with the word “Note” and are set apart from the
   181   normative text with <code class="html">class="note"</code>, like this:
   183   <p class="note">Note, this is an informative note.</p>
   185 <h2 id="processing">Processing of conditional group rules</h2>
   187 <p>This specification defines some CSS @-rules, called <dfn>conditional
   188 group rules</dfn>, that associate a condition with a group of other
   189 CSS rules.  These different rules allow testing different types of
   190 conditions, but share common behavior for how their contents are used
   191 when the condition is true and when the condition is false.</p>
   193 <div class="example">
   194 <p>For example, this rule:</p>
   195 <pre>@media print {
   196   #navigation { display: none }
   197 }</pre>
   198 <p>causes a particular CSS rule (making elements with ID "navigation" be
   199 display:none) apply only when the style sheet is used for a print
   200 medium.
   201 </div>
   203 <p>Each conditional group rule has a condition, which at any time
   204 evaluates to true or false.  When the condition is true, CSS processors
   205 <strong>must</strong> apply the rules inside the group rule as though
   206 they were at the group rule's location; when the condition is false, CSS
   207 processors <strong>must not</strong> apply any of rules inside the group
   208 rule.  The current state of the condition does not affect the CSS object
   209 model, in which the contents of the group rule always remain within the
   210 group rule.</p>
   212 <p>This means that when multiple conditional group rules are nested,
   213 a rule inside of both of them applies only when all of the rules'
   214 conditions are true.</p>
   216 <div class="example">For example, with this set of nested rules:
   217 <pre>@media print { // rule (1)
   218   #navigation { display: none }
   219   @media (max-width: 12cm) { // rule (2)
   220     .note { float: none }
   221   }
   222 }</pre>
   223 the condition of the rule marked (1) is true for print media, and the
   224 condition of the rule marked (2) is true when the width of the display
   225 area (which for print media is the page box) is less than or equal to
   226 12cm.  Thus the rule ''#navigation { display: none }'' applies
   227 whenever this style sheet is applied to print media, and the rule
   228 ''.note { float: none }'' is applied only when the style sheet
   229 is applied to print media <em>and</em> the width of the page box is less
   230 than or equal to 12 centimeters.</div>
   232 <p>When the condition for a conditional group rule changes, CSS
   233 processors <strong>must</strong> reflect that the rules now apply or no
   234 longer apply, except for properties whose definitions define effects of
   235 computed values that persist past the lifetime of that value (such as
   236 for some properties in [[CSS3-TRANSITIONS]] and
   237 [[!CSS3-ANIMATIONS]]).</p>
   239 <h2 id="contents-of">Contents of conditional group rules</h2>
   241 <p>The syntax of each conditional group rule consists of some syntax
   242 specific to the type of rule followed by a <dfn>group rule body</dfn>,
   243 which is a block (pair of braces) containing a sequence of rules.</p>
   245 <p>A group rule body is allowed to contain rulesets and any @-rules that
   246 are allowed at the top level of a style sheet before and after a
   247 ruleset.  This means that @-rules that must occur at the beginning of
   248 the style sheet (such as '@charset', '@import',
   249 and '@namespace' rules) are not allowed inside of conditional group
   250 rules.  Conditional group rules can be nested.</p>
   252 <p>In terms of the grammar, this specification defines the following
   253 productions for use in the grammar of conditional group rules:</p>
   255 <pre><dfn>nested_statement</dfn>
   256   : ruleset | <i>media</i> | page | font_face_rule | keyframes_rule |
   257     <i>supports_rule</i>
   258   ;
   260 <dfn>group_rule_body</dfn>
   261   : '{' S* <i>nested_statement</i>* '}' S*
   262   ;</pre>
   263 <p>
   264 in which all the productions are defined in that grammar with the
   265 exception of <code>font_face_rule</code> 
   266 defined in [[!CSS3-FONTS]], <code>keyframes_rule</code> defined in
   267 [[!CSS3-ANIMATIONS]], and <code>media</code> and <code>supports_rule</code>
   268 defined in this specification.</p>
   270 <p>In general, future CSS specifications that add new @-rules that are
   271 not forbidden to occur after some other types of rules should modify
   272 this <code>nested_statement</code> production to keep the grammar
   273 accurate.</p>
   275 <p>Style sheets <strong>must not</strong> use rules other than the allowed ones inside
   276 conditional group rules.</p>
   278 <p>CSS processors <strong>must</strong> ignore rules that are not
   279 allowed within a group rule, and <strong>must</strong> handle invalid
   280 rules inside of group rules as described in <a
   281 href="http://www.w3.org/TR/CSS21/syndata.html#parsing-errors">section
   282 4.2 (Rules for handling parsing errors)</a>, <a
   283 href="http://www.w3.org/TR/CSS21/syndata.html#at-rules">section 4.1.5
   284 (At-rules)</a>, and <a
   285 href="http://www.w3.org/TR/CSS21/syndata.html#rule-sets">section 4.1.7
   286 (Rule sets, declaration blocks, and selectors)</a> of [[!CSS21]].</p>
   288 <h2 id="use">Placement of conditional group rules</h2>
   290 <p>Conditional group rules are allowed at the top-level of a style
   291 sheet, and inside other conditional group rules.  CSS processors
   292 <strong>must</strong> process such rules as <a
   293 href="#processing">described above</a>.</p>
   295 <p>Any rules that are not allowed after a ruleset (e.g., ''@charset'',
   296 ''@import'', or ''@namespace'' rules) are also not allowed after a
   297 conditional group rule.  Therefore, style sheets <strong>must
   298 not</strong> place such rules after a conditional group rules, and CSS
   299 processors <strong>must</strong> ignore such rules.</p>
   301 <h2 id="at-media">Media-specific style sheets:  the '@media' rule</h2>
   303 <p>The <dfn>'@media' rule</dfn> is a conditional group rule whose
   304 condition is a media query.  It consists of the at-keyword
   305 '@media' followed by a (possibly empty) media query list (as
   306 defined in [[!MEDIAQ]]), followed by a group rule body.  The condition
   307 of the rule is the result of the media query.</p>
   309 <div class="example">
   310 <p>This '@media' rule:</p>
   311 <pre>@media print, (max-width: 600px) {
   312   #extra_navigation { display: none }
   313 }</pre>
   314 <p>has the condition ''print, (max-width: 600px)'', which is
   315 true for print media and for devices whose width is at most 600px.  When
   316 either of these is true, the condition of the rule is true, and the rule
   317 ''#extra_navigation { display: none }'' is applied.
   318 </div>
   320 <p>In terms of the grammar, this specification extends the
   321 <code>media</code> production in the
   322 <a href="http://www.w3.org/TR/CSS21/grammar.html">Grammar of CSS 2.1</a>
   323 ([[!CSS21]], Appendix G) into:
   324 <pre><dfn>media</dfn>
   325   : MEDIA_SYM S* media_query_list <i>group_rule_body</i>
   326   ;</pre>
   327 <p>where the <code>group_rule_body</code> production is defined in this
   328 specification, the <code>media_query_list</code> production is defined
   329 in [[!MEDIAQ]], and the others are defined in the <a
   330 href="http://www.w3.org/TR/CSS21/grammar.html">Grammar of CSS 2.1</a>
   331 ([[!CSS21]], Appendix G).
   333 <h2 id="at-supports">Feature queries: the '@supports' rule</h2>
   335 <p>The <dfn>'@supports' rule</dfn> is a conditional group
   336 rule whose condition tests whether the user agent supports CSS
   337 property:value pairs.  Authors can use it to write style sheets that use
   338 new features when available but degrade gracefully when those features
   339 are not supported.  CSS has existing mechanisms for graceful
   340 degradation, such as ignoring unsupported properties or values, but
   341 these are not always sufficient when large groups of styles need to be
   342 tied to the support for certain features, as is the case for use of new
   343 layout system features.</p>
   345 <p>The syntax of the condition in the '@supports' rule is
   346 slightly more complicated than for the other conditional group rules
   347 (though has some similarities to media queries) since:</p>
   348 <ul>
   349   <li>negation is needed so that the new-feature styles and the fallback
   350   styles can be separated (within the forward-compatible grammar's rules
   351   for the syntax of @-rules), and not required to override each other</li>
   352   <li>conjunction (and) is needed so that multiple required features can
   353   be tested</li>
   354   <li>disjunction (or) is needed when there are multiple alternative
   355   features for a set of styles, particularly when some of those
   356   alternatives are vendor-prefixed properties or values</li>
   357 </ul>
   359 <p>Therefore, the syntax of the '@supports' rule allows
   360 testing for property:value pairs, and arbitrary conjunctions (and),
   361 disjunctions (or), and negations (not) of them.</p>
   363 <p>This extends the lexical scanner in the
   364 <a href="http://www.w3.org/TR/CSS21/grammar.html">Grammar of CSS 2.1</a>
   365 ([[!CSS21]], Appendix G) by adding:
   366 <pre>
   367 @{S}{U}{P}{P}{O}{R}{T}{S} {return SUPPORTS_SYM;}
   368 {O}{R}                    {return OR;}
   369 </pre>
   371 <p>and the grammar by adding</p>
   373 <pre><dfn>supports_rule</dfn>
   374   : SUPPORTS_SYM S* <i>supports_condition</i> <i>group_rule_body</i>
   375   ;
   377 <dfn>supports_condition</dfn>
   378   : <i>supports_negation</i> | <i>supports_conjunction</i> | <i>supports_disjunction</i> |
   379     <i>supports_condition_in_parens</i>
   380   ;
   382 <dfn>supports_condition_in_parens</dfn>
   383   : ( '(' S* <i>supports_condition</i> ')' S* ) | <i>supports_declaration_condition</i> |
   384     <i>general_enclosed</i>
   385   ;
   387 <dfn>supports_negation</dfn>
   388   : NOT S* <i>supports_condition_in_parens</i>
   389   ;
   391 <dfn>supports_conjunction</dfn>
   392   : <i>supports_condition_in_parens</i> ( AND S* <i>supports_condition_in_parens</i> )+
   393   ;
   395 <dfn>supports_disjunction</dfn>
   396   : <i>supports_condition_in_parens</i> ( OR S* <i>supports_condition_in_parens</i> )+
   397   ;
   399 <dfn>supports_declaration_condition</dfn>
   400   : '(' S* declaration ')' S*
   401   ;
   403 <dfn>general_enclosed</dfn>
   404   : ( FUNCTION | '(' ) (any|unused)* ')' S*
   405 </pre>
   407 <p>in which <code>declaration</code>, <code>any</code>, and
   408 <code>unused</code> are the productions in the core syntax of CSS
   409 defined in <a
   410 href="http://www.w3.org/TR/CSS21/syndata.html#tokenization">section
   411 4.1.1 (Tokenization)</a> of [[!CSS21]],
   412 and the <code>AND</code> and <code>NOT</code> tokens are defined in
   413 the Media Queries specification [[!MEDIAQ]].</p>
   415 <p>
   416   Implementations <strong>must</strong> parse ''@supports'' rules
   417   based on the above grammar,
   418   and when interpreting the above grammar,
   419   <strong>must</strong> match the production before an <code>|</code> operator
   420   in preference to the one after it.
   421 </p>
   423 <p>
   424   The above grammar is purposely very loose for forwards-compatibility reasons,
   425   since the <code>general_enclosed</code> production
   426   allows for substantial future extensibility.
   427   Any ''@supports'' rule that does not parse according to the grammar above
   428   (that is, a rule that does not match this loose grammar
   429   which includes the general_enclosed production)
   430   is invalid.
   431   Style sheets <strong>must not</strong> use such a rule and
   432   processors <strong>must</strong> ignore such a rule (including all of its contents).
   434 <p>Each of these grammar terms is associated with a boolean result, as
   435 follows:</p>
   436 <dl>
   437 <dt>supports_condition</dt>
   438 <dd>
   439   The result is the result of the single child term.
   440 </dd>
   442 <dt>supports_condition_in_parens</dt>
   443 <dd>
   444   The result is the result of the single <code>supports_condition</code>
   445   or <code>supports_declaration_condition</code> child term.
   446 </dd>
   448 <dt>supports_negation</dt>
   449 <dd>
   450   The result is the <em>negation</em> of the result of the
   451   <code>supports_condition_in_parens</code> child term.
   452 </dd>
   454 <dt>supports_conjunction</dt>
   455 <dd>
   456   The result is true if the result of <em>all</em> of the
   457   <code>supports_condition_in_parens</code> child terms is true;
   458   otherwise it is false.
   459 </dd>
   461 <dt>supports_disjunction</dt>
   462 <dd>
   463   The result is true if the result of <em>any</em> of the
   464   <code>supports_condition_in_parens</code> child terms is true;
   465   otherwise it is false.
   466 </dd>
   468 <dt>supports_declaration_condition</dt>
   469 <dd>
   470   The result is whether the CSS processor <a href="#support-definition">supports</a> the declaration
   471   within the parentheses.
   472 </dd>
   474 <dt>general_enclosed</dt>
   475 <dd>
   476   The result is always false.
   477   Additionally, style sheets <strong>must not</strong>
   478   write ''@supports'' rules
   479   that match this grammar production.
   480   (In other words, this production exists only for future extensibility,
   481   and is not part of the description of a valid style sheet
   482   in this level of the specification.)
   483   <span class="note">Note that future levels may define functions
   484   or other parenthesized expressions that can evaluate to true.</span>
   485 </dd>
   486 </dl>
   488 <p>The condition of the '@supports' rule is the result of the
   489 <code>supports_condition</code> term that is a child of the
   490 <code>supports_rule</code> term.</p>
   492 <div class="example">
   493 <p>For example, the following rule</p>
   494 <pre>@supports ( display: flexbox ) {
   495   body, #navigation, #content { display: flexbox; }
   496   #navigation { background: blue; color: white; }
   497   #article { background: white; color: black; }
   498 }</pre>
   499 <p>applies the rules inside the '@supports' rule only when
   500 ''display: flexbox'' is supported.</p>
   501 </div>
   503 <div class="example">
   504 <p>The following example shows an additional '@supports' rule that can
   505 be used to provide an alternative for when ''display: flexbox'' is not
   506 supported:</p>
   507 <pre>@supports not ( display: flexbox ) {
   508   body { width: 100%; height: 100%; background: white; color: black; }
   509   #navigation { width: 25%; }
   510   #article { width: 75%; }
   511 }</pre>
   512 <p>Note that the 'width' declarations may be harmful to the
   513 flexbox-based layout, so it is important that they be present only in
   514 the non-flexbox styles.</p>
   515 </div>
   517 <div class="example">
   518 <p>The following example checks for support for the 'box-shadow'
   519 property, including checking for support for vendor-prefixed versions of
   520 it.  When the support is present, it specifies both 'box-shadow' (with
   521 the prefixed versions) and 'color' in a way what would cause the text to
   522 become invisible were 'box-shadow' not supported.</p>
   523 <pre>@supports ( box-shadow: 2px 2px 2px black ) or
   524           ( -moz-box-shadow: 2px 2px 2px black ) or
   525           ( -webkit-box-shadow: 2px 2px 2px black ) or
   526           ( -o-box-shadow: 2px 2px 2px black ) {
   527   .outline {
   528     color: white;
   529     -moz-box-shadow: 2px 2px 2px black;
   530     -webkit-box-shadow: 2px 2px 2px black;
   531     -o-box-shadow: 2px 2px 2px black;
   532     box-shadow: 2px 2px 2px black; /* unprefixed last */
   533   }
   534 }</pre></div>
   536 <p>To avoid confusion between ''and'' and ''or'', the syntax requires
   537 that both ''and'' and ''or'' be specified explicitly (rather than, say,
   538 using commas or spaces for one of them).  Likewise, to avoid confusion
   539 caused by precedence rules, the syntax does not allow ''and'', ''or'',
   540 and ''not'' operators to be mixed without a layer of parentheses.</p>
   542 <div class="example">
   543 <p>For example, the following rule is not valid:
   544 <pre class="illegal">@supports (transition-property: color) or
   545           (animation-name: foo) and
   546           (transform: rotate(10deg)) {
   547   // ...
   548 }</pre>
   549 <p>Instead, authors must write one of the following:</p>
   550 <pre>@supports ((transition-property: color) or
   551            (animation-name: foo)) and
   552           (transform: rotate(10deg)) {
   553   // ...
   554 }</pre>
   555 <pre>@supports (transition-property: color) or
   556           ((animation-name: foo) and
   557            (transform: rotate(10deg))) {
   558   // ...
   559 }</pre>
   560 </div>
   562 <p>The declaration being tested must always occur within parentheses,
   563 when it is the only thing in the expression.<p>
   565 <div class="example">
   566 <p>For example, the following rule is not valid:
   567 <pre class="illegal">@supports display: flexbox {
   568   // ...
   569 }</pre>
   570 <p>Instead, authors must write:</p>
   571 <pre>@supports (display: flexbox) {
   572   // ...
   573 }</pre>
   574 </div>
   576 <p>The syntax allows extra parentheses when they are not needed.  This
   577 flexibility is sometimes useful for authors (for example, when
   578 commenting out parts of an expression) and may also be useful for
   579 authoring tools.</p>
   581 <div class="example">
   582 <p>For example, authors may write:</p>
   583 <pre>@supports ((display: flexbox)) {
   584   // ...
   585 }</pre>
   586 </div>
   588 <p>A trailing ''!important'' on a declaration being tested is allowed,
   589 though it won't change the validity of the declaration.
   591 <div class="example">
   592 <p>For example, the following rule is valid:
   593 <pre>@supports (display: flexbox !important) {
   594   // ...
   595 }</pre>
   596 </div>
   598 <h3 id="support-definition">Definition of support</h3>
   600 <p>For forward-compatibility,
   601 <a href="http://www.w3.org/TR/CSS21/syndata.html#declaration">section 4.1.8
   602 (Declarations and properties)</a> of [[!CSS21]]
   603 defines rules for handling invalid properties and values.
   604 CSS processors that
   605 do not implement or partially implement a specification
   606 <strong>must</strong> treat any part of a value that they
   607 do not implement, or
   608 do not have a usable level of support for,
   609 as invalid according to this rule
   610 for handling invalid properties and values,
   611 and therefore <strong>must</strong> discard the declaration as a parse error.</p>
   613 <p>A CSS processor is considered to <dfn id="dfn-support">support</dfn>
   614 a declaration (consisting of a property and value) if it accepts that
   615 declaration (rather than discarding it as a parse error).
   616 If a processor does not implement, with a usable level of support,
   617 the value given,
   618 then it <strong>must not</strong>
   619 accept the declaration or claim support for it.</p>
   621 <p>These rules (and the equivalence between them) allow
   622 authors to use fallback (either in the [[CSS1]] sense of declarations
   623 that are overridden by later declarations or with the new capabilities
   624 provided by the ''@supports'' rule in this specification) that works
   625 correctly for the features implemented.  This applies especially to
   626 compound values; implementations must implement all parts of the value
   627 in order to consider the declaration supported, either inside a ruleset
   628 or in the declaration condition of an ''@supports'' rule.</p>
   630 <!--
   631 <h2 id="at-document">Document queries: the '@document' rule</h2>
   633 <p>The <dfn>'@document' rule</dfn> is a conditional group
   634 rule whose condition depends on the
   635 <a href="#url-of-doc">URL of the document being styled</a>.
   636 This allows style sheets, particularly user style sheets, to have styles
   637 that only apply to a set of pages rather than to all pages using the
   638 style sheet.</p>
   640 <p class="issue">Given that this @-rule is intended primarily for user
   641 style sheets, what should this specification say about its use in author
   642 style sheets?  Should it be forbidden?  Should use instead be
   643 discouraged?  Or should this specification remain neutral on the
   644 topic, since there are valid uses in author style sheets?</p>
   646 <p id="url-of-doc">The <dfn>URL of the document being styled</dfn> is
   647 the URI at which the document is located, excluding any fragment
   648 identifiers.  (This means, for example, that HTTP redirects have been
   649 followed.)  If the styles are being applied inside a complete document
   650 embedded into the presentation of another (e.g., [[HTML5]]&#39;s <code
   651 class="html">iframe</code>, <code class="html">object</code>, or <code
   652 class="html">img</code> elements), the relevant URI is that of the
   653 frame, not of its container.  However, if content from other documents
   654 is mixed in via mechanisms that mix content from one document into
   655 another (e.g., [[SVG11]]&#39;s <code>use</code> element), then the
   656 address of the container document is used.</p>
   658 <p class="note">Note:  In [[HTML5]], this is the
   659 <a href="http://dev.w3.org/html5/spec/dom.html#documents">document's address</a>
   660 of a document in a
   661 <a href="http://dev.w3.org/html5/spec/browsers.html#browsing-context">browsing context</a>.</p>
   663 <div class="issue">What form of normalization is done on URLs and domains
   664 before matching?  In particular, this specification needs to describe:
   665 <ul>
   666 <li>what form is used for the <a href="#url-of-doc">URL of the document
   667 being styled</a> (and what has been normalized in that form)</li>
   668 <li>what normalization (if any) happens to the argument of each of the match
   669 functions before the comparison that they describe and</li>
   670 <li>whether the
   671 comparison algorithm used is string comparison or some other URL
   672 comparison algorithm.</li></ul></div>
   674 <p>The '@document' rule's condition is written as a
   675 comma-separated list of <dfn>URL matching functions</dfn>, and the
   676 condition evaluates to true whenever any one of those functions
   677 evaluates to true.  The following URL matching functions are
   678 permitted:</p>
   680 <dl>
   681   <dt><dfn id="url-exact" title="url()|URL matching functions::exact">&lt;url&gt;</dfn></dt>
   683   <dd>
   684     <p>The 'url()' function is the <dfn>exact url matching
   685     function</dfn>.  It evaluates to true whenever the <a
   686     href="#url-of-doc">URL of the document being styled</a> is exactly
   687     the URL given.</p>
   689     <p class="Note">The 'url()' function, since it is a core syntax
   690     element in CSS, is allowed (subject to different character
   691     limitations and thus escaping requirements) to contain an unquoted
   692     value (in addition to the string values that are allowed as
   693     arguments for all four functions).</p>
   695     <div class="example">
   696       <p>For example, this rule:</p>
   697 <pre>@document url("http://www.w3.org/Style/CSS/") {
   698   #summary { background: yellow; color: black}
   699 }</pre>
   700       <p>styles the <code class="html">summary</code> element on the page
   701       <code>http://www.w3.org/Style/CSS/</code>, but not on any other
   702       pages.</p>
   703     </div>
   704   </dd>
   706   <dt><dfn id="url-prefix" title="url-prefix()|URL matching functions::prefix">url-prefix(&lt;string&gt;)</dfn></dt>
   708   <dd>
   709     <p>The 'url-prefix()' function is the <dfn>url prefix
   710     matching function</dfn>.  It evaluates to true whenever the
   711     <a href="#url-of-doc">URL of the document being styled</a>
   712     has the argument to the function as an
   713     initial substring (which is true when the two strings are equal).
   714     When the argument is the empty string, it evaluates to true for all
   715     documents.</p>
   716     <div class="example">
   717       <p>For example, this rule:</p>
   718 <pre>@document url-prefix("http://www.w3.org/Style/CSS/") {
   719   #summary { background: yellow; color: black}
   720 }</pre>
   721       <p>styles the <code class="html">summary</code> element on the page
   722       <code>http://www.w3.org/Style/CSS/</code> and on the page
   723       <code>http://www.w3.org/Style/CSS/Test</code>, but it does not
   724       affect the page <code>http://www.w3.org/</code> or the page
   725       <code>http://www.example.com/Style/CSS/</code>.</p>
   726     </div>
   727   </dd>
   729   <dt><dfn id="url-domain" title="domain()|URL matching functions::domain">domain(&lt;string&gt;)</dfn></dt>
   731   <dd>
   732     <p>The 'domain()' function is the <dfn>domain
   733     matching function</dfn>.  It evaluates to true whenever
   734     the <a href="#url-of-doc">URL of the document being styled</a>
   735     has a host subcomponent (as defined in [[!URI]])
   736     and that host subcomponent is exactly the argument to the
   737     'domain()' function or a final substring of the host
   738     component is a period (U+002E) immediately followed by the argument
   739     to the 'domain()' function.</p>
   740     <div class="example">
   741       <p>For example, this rule:</p>
   742 <pre>@document domain("w3.org") {
   743   body { font-size: 16px ! important }
   744 }</pre>
   745       <p>changes the font size of the body element for pages such as
   746       <code>http://www.w3.org/Style/CSS/</code> and
   747       <code>http://w3.org/Style/CSS/</code> and
   748       <code>http://lists.w3.org/Archives/Public/www-style/</code>
   749       but it does not affect the page
   750       <code>http://www.example.com/Style/CSS/</code>.</p>
   751     </div>
   752   </dd>
   754   <dt><dfn id="url-regexp" title="regexp()|URL matching functions::regular expression">regexp(&lt;string&gt;)</dfn></dt>
   756   <dd>
   757     <p>The contents of the &lt;string&gt; argument <strong>must</strong>
   758     match the JavaScript <code>Pattern</code> production
   759     ([[!ECMA-262-5.1]], section 15.10.1).  However,
   760     failing to do so is not a CSS syntax error and does not trigger any
   761     error handling for CSS syntax errors.</p>
   763     <p>The ''regexp()'' function evaluates to true whenever the string
   764     argument compiled as a JavaScript regular expression with the
   765     <code>global</code>, <code>ignoreCase</code> and
   766     <code>multiline</code> flags <em>disabled</em>
   767     (see [[!ECMA-262-5.1]], sections 15.10.7.2 through 15.10.7.4)
   768     compiles successfully and the resulting regular expression matches
   769     the entirety of the
   770     <a href="#url-of-doc">URL of the document being styled</a>.</p>
   772     <p class="note">Note that regular expression must match the entire
   773     URL, not just a part of it.</p>
   775     <p class="note">Note that this definition intentionally matches the
   776     behavior of the <a
   777     href="http://dev.w3.org/html5/spec/common-input-element-attributes.html#attr-input-pattern"><code class="html">pattern</code>
   778     attribute</a> on the <code class="html">input</code> element
   779     in [[HTML5]].</p>
   781     <div class="example">
   782       <p>For example, this rule:</p>
   783 <pre>@document regexp("http://www.w3.org/TR/\\d{4}/[^/]*-CSS2-\\d{8}/") {
   784   body { font-size: 20px ! important }
   785 }</pre>
   786       <p>changes the font size of the body element for pages such as
   787       <code>http://www.w3.org/TR/2011/PR-CSS2-20110412/</code>.</p>
   788       <p class="note">Note that the backslashes in the regular
   789       expression require CSS escaping as ''\\''.</p>
   790     </div>
   791   </dd>
   793 </dl>
   795 <p>Implementations <strong>must</strong> treat any unknown URL matching
   796 functions as a syntax error, and thus ignore the '@document' rule.
   797 <span class="issue">Should we instead have more complicated error
   798 handling rules to make forward-compatibility work differently, or is
   799 this rule the best solution for such future expansion anyway?</span></p>
   801 <div class="issue">This syntax doesn't offer any ability to do negations,
   802 which has been requested in <a
   803 href="https://bugzilla.mozilla.org/show_bug.cgi?id=349813">Mozilla bug
   804 349813</a>.  Use cases that people have wanted negations for
   805 include:
   806 <ul>
   807   <li>User style sheets that want a particular rule in general, but know
   808   that that rule does more harm than good on specific sites.</li>
   809   <li>Authors who have a rule that they want to apply to most of their
   810   pages, but wish to make a few exceptions for.</li>
   811 </ul>
   812 </div>
   814 <p>This extends the lexical scanner in the
   815 <a href="http://www.w3.org/TR/CSS21/grammar.html">Grammar of CSS 2.1</a>
   816 ([[!CSS21]], Appendix G) by adding:
   817 <pre>@{D}{O}{C}{U}{M}{E}{N}{T}	{return DOCUMENT_SYM;}</pre>
   818 <p>and the grammar by adding</p>
   819 <pre><dfn>document_rule</dfn>
   820   : DOCUMENT_SYM S+ <i>url_match_fn</i> ( "," S* <i>url_match_fn</i> )* <i>group_rule_body</i>
   821   ;
   823 <dfn>url_match_fn</dfn>
   824   : (URI | FUNCTION S* STRING S* ')' ) S*
   825   ;</pre>
   826 -->
   829 <h2 id="apis">APIs</h2>
   831 <h3 id='extentions-to-cssrule-interface'>
   832 Extensions to the <code>CSSRule</code> interface</h3>
   834 <p>The <code>CSSRule</code> interface is extended as follows:
   836 <pre class='idl'>partial interface CSSRule {
   837     const unsigned short SUPPORTS_RULE = 12;
   838     <!--
   839     const unsigned short DOCUMENT_RULE = 13;
   840     -->
   841 }</pre>
   844 <h3 id='the-cssgroupingrule-interface'>
   845 The <code>CSSGroupingRule</code> interface</h3>
   847 <p>The <dfn><code>CSSGroupingRule</code></dfn> interface represents an at-rule that contains other rules nested inside itself.
   849 <pre class='idl'>interface CSSGroupingRule : CSSRule {
   850     readonly attribute CSSRuleList cssRules;
   851     unsigned long insertRule (DOMString rule, unsigned long index);
   852     void deleteRule (unsigned long index);
   853 }</pre>
   855 <dl class='idl-attributes'>
   856   <dt><code>cssRules</code> of type <code>CSSRuleList</code>, readonly
   857   <dd>The <code>cssRules</code> attribute must return a <code>CSSRuleList</code>
   858     object for the list of CSS rules nested inside the grouping rule.
   859 </dl>
   861 <dl class='idl-methods'>
   862   <dt><code>insertRule(DOMString rule, unsigned long index)</code>, returns
   863     <code>unsigned long</code>
   864   <dd>The <code>insertRule</code> operation must insert a CSS rule <var>rule</var>
   865     into the CSS rule list returned by <code>cssRules</code> at <var>index</var>.
   867   <dt><code>deleteRule (unsigned long index)</code>, return <code>void</code>
   868   <dd>The <code>deleteRule</code> operation must remove a CSS rule from the 
   869     CSS rule list returned by <code>cssRules</code> at <var>index</var>.
   870 </dl>
   873 <h3 id="the-cssconditionrule-interface">
   874 The <code>CSSConditionRule</code> interface</h3>
   876 <p>The <dfn><code>CSSConditionRule</code></dfn> interface represents all the "conditional" at-rules,
   877   which consist of a condition and a statement block.
   879 <pre class='idl'>interface CSSConditionRule : CSSGroupingRule {
   880     attribute DOMString conditionText;
   881 }</pre>
   883 <dl class='idl-attributes'>
   885   <dt><code>conditionText</code> of type <code>DOMString</code>
   886   <dd>
   887     <p>The <code>conditionText</code> attribute represents
   888     the condition of the rule.
   889     Since what this condition does
   890     varies between the derived interfaces of <code>CSSConditionRule</code>,
   891     those derived interfaces
   892     may specify different behavior for this attribute
   893     (see, for example, <code>CSSMediaRule</code> below).
   894     In the absence of such rule-specific behavior,
   895     the following rules apply:</p>
   897     <p>The <code>conditionText</code> attribute, on getting, must return
   898     the result of serializing the associated condition.
   900     <p>On setting the <code>conditionText</code> attribute these steps
   901       must be run:
   903     <ol>
   904       <li>Trim the given value of white space.
   905       <li>If the given value matches the grammar of the 
   906         appropriate condition production for the given rule, 
   907         replace the associated CSS condition with the given value.
   908       <li>Otherwise, do nothing.
   909     </ol>
   910 </dl>
   913 <h3 id="the-cssmediarule-interface">
   914 The <code>CSSMediaRule</code> interface</h3>
   916 <p>The <dfn><code>CSSMediaRule</code></dfn> interface represents a ''@media'' rule:
   918 <pre class='idl'>interface CSSMediaRule : CSSConditionRule {
   919     readonly attribute MediaList media;
   920 }</pre>
   922 <dl class='idl-attributes'>
   923   <dt><code>media</code> of type <code>MediaList</code>, readonly
   924   <dd>The <code>media</code> attribute must return a <code>MediaList</code> object
   925     for the list of media queries specified with the ''@media'' rule.
   927   <dt><code>conditionText</code> of type <code>DOMString</code>
   928   <dd>The <code>conditionText</code> attribute (defined on the <code>CSSConditionRule</code> parent rule),
   929     on getting, must return the value of <code>media.mediaText</code> on the rule.
   931     <p>Setting the <code>conditionText</code> attribute
   932       must set the <code>media.mediaText</code> attribute on the rule.
   933 </dl>
   936 <h3 id="the-csssupportsrule-interface">
   937 The <code>CSSSupportsRule</code> interface</h3>
   939 <p>The <dfn><code>CSSSupportsRule</code></dfn> interface represents a ''@supports'' rule.</p>
   941 <pre class='idl'>interface CSSSupportsRule : CSSConditionRule {
   942 }</pre>
   944 <!--
   945 <h3 id="the-cssdocumentrule-interface">
   946 The <code>CSSDocumentRule</code> interface</h3>
   948 <p>The <dfn><code>CSSDocumentRule</code></dfn> interface represents a ''@document'' rule.</p>
   950 <pre class='idl'>interface CSSDocumentRule : CSSConditionRule {
   951 }</pre>
   952 -->
   955 <h3 id='the-css-interface'>
   956 The <code>CSS</code> interface, and the <code title=''>supports()</code> function</h3>
   958 <p>The <dfn id='CSS-interface'><code>CSS</code></dfn> interface holds useful CSS-related functions that do not belong elsewhere.
   960 <pre class='idl'>interface CSS {
   961   boolean supports(DOMString property, DOMString value);
   962   boolean supports(DOMString declaration);
   963 }</pre>
   965 <dl class='idl-methods'>
   966   <dt><code>supports(DOMString property, DOMString value)</code>,
   967     returns <code>boolean</code>
   968   <dt><code>supports(DOMString conditionText)</code>,
   969     returns <code>boolean</code>
   970   <dd>
   971     When the <code title=''>supports()</code> method is invoked with two arguments <var>property</var> and <var>value</var>,
   972     it must return <code>true</code> if <var>property</var> is a literal match for the name of a CSS property that the UA supports,
   973     and <var>value</var> would be successfully parsed as a supported value for that property.
   974     Otherwise, it must return <code>false</code>.
   976     <p>
   977       When invoked with a single <var>conditionText</var> argument,
   978       it must return <code>true</code> if <var>conditionText</var>,
   979       when parsed and evaluated as a <code>supports_condition</code>,
   980       would return true.
   981       Otherwise, it must return <code>false</code>.
   982   </dl>
   985 <h2 class=no-num id="grammar">Grammar</h2>
   987 <p>In order to allow these new @-rules in CSS style sheets, this
   988 specification modifies the <code>stylesheet</code> production in the <a
   989 href="http://www.w3.org/TR/CSS21/grammar.html">Appendix G</a> grammar of
   990 [[!CSS21]] by replacing the <code>media</code> production defined in
   991 [[!CSS21]] with the <code>media</code> production defined in this one,
   992 and additionally inserting <code>| supports_rule</code>
   993 alongside <code>ruleset | media | page</code>.</p>
   996 <h2 id="conformance">Conformance</h2>
   998 <h3 id="base-modules">Base Modules</h3>
  1000 <p>This specification defines conformance in terms of base modules,
  1001 which are modules that this specification builds on top of.  The base
  1002 modules of this module are:</p>
  1004 <ul>
  1005 <li>[[!CSS21]]</li>
  1006 </ul>
  1008 <p>All of the conformance requirements of all base modules are
  1009 incorporated as conformance requirements of this module, except where
  1010 overridden by this module.</p>
  1012 <p>Additionally, all conformance requirements related to validity of
  1013 syntax in this module and all of its base modules are to be interpreted
  1014 as though all syntax in all of those modules is valid.</p>
  1016 <div class="example"><p>For example, this means that grammar presented
  1017 in modules other than [[!CSS21]] must obey the requirements that
  1018 [[!CSS21]] defines for the parsing of properties, and that requirements
  1019 for handling invalid syntax in [[!CSS21]] do not treat syntax added by
  1020 other modules as invalid.</p></div>
  1022 <p>Additionally, the set of valid syntax can be increased by the
  1023 conformance of a style sheet or processor to additional modules; use of
  1024 such syntax does not make a style sheet nonconformant and failure to
  1025 treat such syntax as invalid does not make a processor
  1026 nonconformant.</p>
  1028 <h3 id="conformance-classes">Conformance Classes</h3>
  1030   <p>Conformance to the CSS Conditional Rules Module is defined for three
  1031   conformance classes:
  1032   <dl>
  1033     <dt><dfn title="conformance::style sheet" id="conform-style-sheet">style sheet</dfn>
  1034       <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
  1035       style sheet</a>.</dd>
  1036     <dt><dfn title="conformance::processor" id="conform-processor">processor</dfn></dt>
  1037       <dd>A tool that reads CSS style sheets:  it may be a renderer or
  1038       <a
  1039       href="http://www.w3.org/TR/CSS21/conform.html#user-agent">user-agent</a>
  1040       that interprets the semantics of a style sheet and renders
  1041       documents that use style sheets, or it may be a validator that
  1042       checks style sheets.</dd>
  1043     <dt><dfn title="conformance::authoring tool" id="conform-authoring-tool">authoring tool</dfn></dt>
  1044       <dd>A tool that writes a style sheet.</dd>
  1045   </dl>
  1047   <p>A style sheet is conformant to the CSS Conditional Rules Module
  1048   if it meets all of the conformance requirements in the module that are
  1049   described as requirements of style sheets.</p>
  1051   <p>A processor is conformant to the CSS Conditional Rules Module if it
  1052   meets all applicable conformance requirements in the module that are
  1053   described as requirements of processors.  In general, all requirements
  1054   are applicable to renderers.  Requirements concerning a part of CSS
  1055   not performed by a processor are not applicable, e.g., requirements
  1056   related to rendering are not applicable to a validator.  The inability
  1057   of a processor to correctly render a document due to limitations of
  1058   the device does not make it non-conformant. (For example, a renderer
  1059   is not required to render color on a monochrome monitor.)</p>
  1061   <p>An authoring tool is conformant to the CSS Conditional Rules Module
  1062   if it writes style sheets that conform to the module and (if it reads
  1063   CSS) it is a conformant processor.</p>
  1065 <h3 id="partial">
  1066 Partial Implementations</h3>
  1068   <p>So that authors can exploit the forward-compatible parsing rules to
  1069   assign fallback values, CSS renderers <strong>must</strong>
  1070   treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore
  1071   as appropriate</a>) any at-rules, properties, property values, keywords,
  1072   and other syntactic constructs for which they have no usable level of
  1073   support. In particular, user agents <strong>must not</strong> selectively
  1074   ignore unsupported component values and honor supported values in a single
  1075   multi-value property declaration: if any value is considered invalid
  1076   (as unsupported values must be), CSS requires that the entire declaration
  1077   be ignored.</p>
  1079 <h3 id="experimental">Experimental Implementations</h3>
  1081   <p>To avoid clashes with future CSS features, the CSS specifications
  1082   reserve a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
  1083   syntax</a> for proprietary property and value extensions to CSS. The CSS
  1084   Working Group recommends that experimental implementations of features in
  1085   CSS Working Drafts also use vendor-prefixed property or value names. This
  1086   avoids any incompatibilities with future changes in the draft. Once a
  1087   specification reaches the Candidate Recommendation stage, implementors
  1088   should implement the non-prefixed syntax for any feature they consider to
  1089   be correctly implemented according to spec.</p>
  1091 <h3 id="cr-exit-criteria">CR Exit Criteria</h3>
  1093   <p>For this specification to be advanced to Proposed Recommendation,
  1094   there must be at least two independent, interoperable implementations
  1095   of each feature. Each feature may be implemented by a different set of
  1096   products, there is no requirement that all features be implemented by
  1097   a single product. For the purposes of this criterion, we define the
  1098   following terms:
  1100   <dl>
  1101     <dt>independent <dd>each implementation must be developed by a
  1102     different party and cannot share, reuse, or derive from code
  1103     used by another qualifying implementation. Sections of code that
  1104     have no bearing on the implementation of this specification are
  1105     exempt from this requirement.
  1107     <dt>interoperable <dd>passing the respective test case(s) in the
  1108     official CSS test suite, or, if the implementation is not a Web
  1109     browser, an equivalent test. Every relevant test in the test
  1110     suite should have an equivalent test created if such a user
  1111     agent (UA) is to be used to claim interoperability. In addition
  1112     if such a UA is to be used to claim interoperability, then there
  1113     must one or more additional UAs which can also pass those
  1114     equivalent tests in the same way for the purpose of
  1115     interoperability. The equivalent tests must be made publicly
  1116     available for the purposes of peer review.
  1118     <dt>implementation <dd>a user agent which:
  1120     <ol class=inline>
  1121       <li>implements the specification.
  1123       <li>is available to the general public. The implementation may
  1124       be a shipping product or other publicly available version
  1125       (i.e., beta version, preview release, or “nightly build”). 
  1126       Non-shipping product releases must have implemented the
  1127       feature(s) for a period of at least one month in order to
  1128       demonstrate stability.
  1130       <li>is not experimental (i.e., a version specifically designed
  1131       to pass the test suite and is not intended for normal usage
  1132       going forward).
  1133     </ol>
  1134   </dl>
  1136   <p>The specification will remain Candidate Recommendation for at least
  1137   six months.
  1139 <h2 id="changes">
  1140 Changes</h2>
  1142 <p>The following (non-editorial) changes were made to this specification since the
  1143 <a href="http://www.w3.org/TR/2012/WD-css3-conditional-20120911/">11 September 2012 Working Draft</a>:
  1145 <ul>
  1146   <li>Removed ''@document'' rule; it has been deferred to Level 4.
  1147   <li>Allow functional notation in ''@supports'' queries to be valid (to allow for future extensions),
  1148       but treat such notations as always being false.
  1149   <li>Corrected the grammar as follows:
  1150 <pre>
  1151 -  : SUPPORTS_SYM S+ supports_condition group_rule_body
  1152 +  : SUPPORTS_SYM S* supports_condition group_rule_body
  1153 </pre>
  1154 <pre>
  1155 -  : (URI | FUNCTION) S*
  1156 +  : (URI | FUNCTION S* STRING S* ')' ) S*
  1157 </pre>
  1158   <li>Switched "and", "or", and "not" keywords to use appropriate productions rather than literals.
  1159   <li>Clarified definition of support used for interpreting ''@support'' rules
  1160   and its relationship to CSS forwards-compatible parsing rules.
  1161 </ul>
  1163 <h2 class=no-num id="acknowledgments">Acknowledgments</h2>
  1165 <p>
  1166 Thanks to the ideas and feedback from
  1167 Tab Atkins,
  1168 <span lang="tr">Tantek Çelik</span>,
  1169 Alex Danilo,
  1170 Elika Etemad,
  1171 Pascal Germroth,
  1172 <span lang="de">Björn Höhrmann</span>,
  1173 Paul Irish,
  1174 Vitor Menezes,
  1175 Alex Mogilevsky,
  1176 Chris Moschini,
  1177 Simon Sapin,
  1178 Ben Ward,
  1179 Zack Weinberg,
  1180 Estelle Weyl,
  1181 Boris Zbarsky,
  1182 and all the rest of the <a href="http://lists.w3.org/Archives/Public/www-style/">www-style</a> community.
  1184 </p>
  1186 <h2 class=no-num id="references">References</h2>
  1189 <h3 class="no-num" id="normative-references">Normative references</h3>
  1190 <!--normative-->
  1192 <h3 class="no-num" id="other-references">Other references</h3>
  1193 <!--informative-->
  1195 <h2 class="no-num" id="index">Index</h2>
  1196 <!--index-->
  1198 </body>
  1199 </html>
  1200 <!-- Keep this comment at the end of the file
  1201 Local variables:
  1202 mode: sgml
  1203 sgml-declaration:"~/SGML/HTML4.decl"
  1204 sgml-default-doctype-name:"html"
  1205 sgml-minimize-attributes:t
  1206 sgml-nofill-elements:("pre" "style" "br")
  1207 sgml-live-element-indicator:t
  1208 sgml-omittag:nil
  1209 sgml-shorttag:nil
  1210 sgml-namecase-general:t
  1211 sgml-general-insert-case:lower
  1212 sgml-always-quote-attributes:t
  1213 sgml-indent-step:nil
  1214 sgml-indent-data:t
  1215 sgml-parent-document:nil
  1216 sgml-exposed-tags:nil
  1217 sgml-local-catalogs:nil
  1218 sgml-local-ecat-files:nil
  1219 End:
  1220 -->

mercurial