Thu, 07 Feb 2013 11:58:14 -0800
[css3-syntax] Remove trailing whitespace
Sorry for the commit noise. My editor normalizes this automatically.
css3-syntax/Overview.src.html | file | annotate | diff | comparison | revisions |
1.1 --- a/css3-syntax/Overview.src.html Thu Feb 07 23:25:50 2013 -0800 1.2 +++ b/css3-syntax/Overview.src.html Thu Feb 07 11:58:14 2013 -0800 1.3 @@ -40,7 +40,7 @@ 1.4 1.5 <dt>Feedback: 1.6 <dd> 1.7 - <a href="http://lists.w3.org/Archives/Public/www-style/">www-style@w3.org</a> 1.8 + <a href="http://lists.w3.org/Archives/Public/www-style/">www-style@w3.org</a> 1.9 with subject line “<kbd>[css3-syntax] <var>… message topic …</var></kbd>” 1.10 1.11 <dt>Editors: 1.12 @@ -59,9 +59,9 @@ 1.13 <h2 class="no-num no-toc" id="abstract">Abstract</h2> 1.14 1.15 <p> 1.16 - <a href="http://www.w3.org/TR/CSS/">CSS</a> is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. 1.17 + <a href="http://www.w3.org/TR/CSS/">CSS</a> is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. 1.18 This module describes, in general terms, the basic structure and syntax of CSS stylesheets. 1.19 - It defines, in detail, the syntax and parsing of CSS - how to turn a stream of bytes into a meaningful stylesheet. 1.20 + It defines, in detail, the syntax and parsing of CSS - how to turn a stream of bytes into a meaningful stylesheet. 1.21 1.22 <h2 class="no-num no-toc" id="status">Status of this document</h2> 1.23 1.24 @@ -85,7 +85,7 @@ 1.25 (such as the HTML <code>style</code> attribute). 1.26 1.27 <p> 1.28 - It defines algorithms for converting a stream of codepoints 1.29 + It defines algorithms for converting a stream of codepoints 1.30 (in other words, text) 1.31 into a stream of CSS tokens, 1.32 and then further into CSS objects 1.33 @@ -104,9 +104,9 @@ 1.34 <p><em>This section is not normative.</em> 1.35 1.36 <p> 1.37 - A CSS document is a series of <i>style rules</i>, 1.38 - which apply CSS properties to elements in the source document, 1.39 - and <i>at-rules</i>, 1.40 + A CSS document is a series of <i>style rules</i>, 1.41 + which apply CSS properties to elements in the source document, 1.42 + and <i>at-rules</i>, 1.43 which define special processing rules or values for the CSS document. 1.44 1.45 <p> 1.46 @@ -114,7 +114,7 @@ 1.47 (defined by the <a href="http://www.w3.org/TR/selectors/">Selectors specification</a>), 1.48 then has a {}-wrapped block containing a sequence of declarations. 1.49 The selector specifies which elements the declarations will apply to. 1.50 - Each declaration has a property name, 1.51 + Each declaration has a property name, 1.52 followed by a colon and the property value, 1.53 and finished with a semicolon. 1.54 1.55 @@ -123,7 +123,7 @@ 1.56 A typical rule might look something like this: 1.57 1.58 <pre> 1.59 -p > a { 1.60 +p > a { 1.61 color: blue; 1.62 text-decoration: underline; 1.63 }</pre> 1.64 @@ -134,7 +134,7 @@ 1.65 selects any <code><a></code> elements that are children of a <code><p></code> element. 1.66 1.67 <p> 1.68 - "<code>color: blue;</code>" is a declaration specifying that, 1.69 + "<code>color: blue;</code>" is a declaration specifying that, 1.70 for the elements that match the selector, 1.71 their 'color' property should have the value ''blue''. 1.72 Similiarly, their 'text-decoration' property should have the value ''underline''. 1.73 @@ -147,7 +147,7 @@ 1.74 with their name followed by more CSS values to specify their behavior, 1.75 and finally ended by a semicolon. 1.76 Others are blocks; 1.77 - they can have CSS values following their name, 1.78 + they can have CSS values following their name, 1.79 but they end with a {}-wrapped block, 1.80 similar to a <i>rule</i>. 1.81 Even the contents of these blocks are specific to the given <i>at-rule</i>: 1.82 @@ -201,50 +201,50 @@ 1.83 The syntax of selectors is defined in the <a href="http://www.w3.org/TR/selectors/">Selectors spec</a>. 1.84 Similarly, the syntax of the wide variety of CSS values is defined in the <a href="http://www.w3.org/TR/css3-values/">Values & Units spec</a>. 1.85 The special syntaxes of individual <i>at-rules</i> can be found in the specs that define them. 1.86 - 1.87 + 1.88 <h2> 1.89 Tokenizing and Parsing CSS</h2> 1.90 1.91 <p> 1.92 - User agents must use the parsing rules described in this specifiction 1.93 - to generate the CSSOM trees from text/css resources. 1.94 + User agents must use the parsing rules described in this specifiction 1.95 + to generate the CSSOM trees from text/css resources. 1.96 Together, these rules define what is referred to as the CSS parser. 1.97 1.98 <p> 1.99 - This specification defines the parsing rules for CSS documents, 1.100 - whether they are syntactically correct or not. 1.101 - Certain points in the parsing algorithm are said to be parse errors. 1.102 - The error handling for parse errors is well-defined: 1.103 - user agents must either act as described below when encountering such problems, 1.104 + This specification defines the parsing rules for CSS documents, 1.105 + whether they are syntactically correct or not. 1.106 + Certain points in the parsing algorithm are said to be parse errors. 1.107 + The error handling for parse errors is well-defined: 1.108 + user agents must either act as described below when encountering such problems, 1.109 or must abort processing at the first error that they encounter for which they do not wish to apply the rules described below. 1.110 1.111 <p> 1.112 - Conformance checkers must report at least one parse error condition to the user 1.113 - if one or more parse error conditions exist in the document 1.114 - and must not report parse error conditions 1.115 - if none exist in the document. 1.116 - Conformance checkers may report more than one parse error condition if more than one parse error condition exists in the document. 1.117 + Conformance checkers must report at least one parse error condition to the user 1.118 + if one or more parse error conditions exist in the document 1.119 + and must not report parse error conditions 1.120 + if none exist in the document. 1.121 + Conformance checkers may report more than one parse error condition if more than one parse error condition exists in the document. 1.122 Conformance checkers are not required to recover from parse errors. 1.123 1.124 <h3> 1.125 Overview of the Parsing Model</h3> 1.126 1.127 <p> 1.128 - The input to the CSS parsing process consists of a stream of Unicode code points, 1.129 - which is passed through a tokenization stage followed by a tree construction stage. 1.130 + The input to the CSS parsing process consists of a stream of Unicode code points, 1.131 + which is passed through a tokenization stage followed by a tree construction stage. 1.132 The output is a CSSStyleSheet object. 1.133 1.134 <p class='note'> 1.135 - Implementations that do not support scripting do not have to actually create a CSSOM CSSStyleSheet object, 1.136 + Implementations that do not support scripting do not have to actually create a CSSOM CSSStyleSheet object, 1.137 but the CSSOM tree in such cases is still used as the model for the rest of the specification. 1.138 1.139 <h3> 1.140 The input byte stream</h3> 1.141 1.142 <p> 1.143 - The stream of Unicode code points that comprises the input to the tokenization stage will be initially seen by the user agent as a stream of bytes 1.144 - (typically coming over the network or from the local file system). 1.145 - The bytes encode the actual characters according to a particular character encoding, 1.146 + The stream of Unicode code points that comprises the input to the tokenization stage will be initially seen by the user agent as a stream of bytes 1.147 + (typically coming over the network or from the local file system). 1.148 + The bytes encode the actual characters according to a particular character encoding, 1.149 which the user agent must use to decode the bytes into characters. 1.150 1.151 <p> 1.152 @@ -252,8 +252,8 @@ 1.153 UAs must follow these steps. 1.154 1.155 <p> 1.156 - The algorithms to <a href="http://encoding.spec.whatwg.org/#concept-encoding-get"><dfn>get an encoding</dfn></a> 1.157 - and <a href="http://encoding.spec.whatwg.org/#decode"><dfn>decode</dfn></a> 1.158 + The algorithms to <a href="http://encoding.spec.whatwg.org/#concept-encoding-get"><dfn>get an encoding</dfn></a> 1.159 + and <a href="http://encoding.spec.whatwg.org/#decode"><dfn>decode</dfn></a> 1.160 are defined in the <a href="http://encoding.spec.whatwg.org/">Encoding Standard</a>. 1.161 1.162 <ol> 1.163 @@ -261,7 +261,7 @@ 1.164 Let <var>encoding</var> be utf-8. 1.165 1.166 <li> 1.167 - If HTTP or equivalent protocol defines an encoding (e.g. via the charset parameter of the Content-Type header), 1.168 + If HTTP or equivalent protocol defines an encoding (e.g. via the charset parameter of the Content-Type header), 1.169 <i>get an encoding</i> for the specified value. 1.170 If that does not return failure, 1.171 set <var>encoding</var> to the return value 1.172 @@ -271,7 +271,7 @@ 1.173 Check the byte stream. If the first several bytes match the hex sequence 1.174 1.175 <pre>40 63 68 61 72 73 65 74 20 22 (XX)* 22 3B</pre> 1.176 - 1.177 + 1.178 then <i>get an encoding</i> for the sequence of XX bytes, 1.179 decoded per <code>windows-1252</code>, 1.180 and let <var>temp</var> be the return value. 1.181 @@ -286,7 +286,7 @@ 1.182 where the "…" is the sequence of bytes corresponding to the encoding's name. 1.183 1.184 <p> 1.185 - If <var>temp</var> is <code>utf-16</code> or <code>utf-16be</code>, 1.186 + If <var>temp</var> is <code>utf-16</code> or <code>utf-16be</code>, 1.187 set <var>temp</var> to <code>utf-8</code>. 1.188 If <var>temp</var> is not failure, 1.189 set <var>encoding</var> to it 1.190 @@ -331,8 +331,8 @@ 1.191 1.192 <ul> 1.193 <li> 1.194 - Replace any U+000D CARRIAGE RETURN (CR) characters 1.195 - or pairs of U+000D CARRIAGE RETURN (CR) followed by U+000A LINE FEED (LF) 1.196 + Replace any U+000D CARRIAGE RETURN (CR) characters 1.197 + or pairs of U+000D CARRIAGE RETURN (CR) followed by U+000A LINE FEED (LF) 1.198 by a single U+000A LINE FEED (LF) character. 1.199 1.200 <li> 1.201 @@ -350,13 +350,13 @@ 1.202 Tokenization</h2> 1.203 1.204 <p> 1.205 - Implementations must act as if they used the following state machine to tokenize CSS. 1.206 - The state machine must start in the <i>data state</i>. 1.207 - Most states consume a single character, 1.208 - which may have various side-effects, 1.209 - and either switches the state machine to a new state to reconsume the same character, 1.210 - or switches it to a new state to consume the next character, 1.211 - or stays in the same state to consume the next character. 1.212 + Implementations must act as if they used the following state machine to tokenize CSS. 1.213 + The state machine must start in the <i>data state</i>. 1.214 + Most states consume a single character, 1.215 + which may have various side-effects, 1.216 + and either switches the state machine to a new state to reconsume the same character, 1.217 + or switches it to a new state to consume the next character, 1.218 + or stays in the same state to consume the next character. 1.219 Some states have more complicated behavior and can consume several characters before switching to another state. 1.220 1.221 <p> 1.222 @@ -399,7 +399,7 @@ 1.223 Unicode-range tokens have a range of characters. 1.224 1.225 <p class='issue'> 1.226 - Several types of tokens that are guaranteed to be language-defined, 1.227 + Several types of tokens that are guaranteed to be language-defined, 1.228 like at-keywords, functions, or dimension units, 1.229 are always lowercased when serialized. 1.230 Should we eagerly lowercase them in the parser, 1.231 @@ -506,7 +506,7 @@ 1.232 <dt><dfn>hex digit</dfn> 1.233 <dd> 1.234 A <i>digit</i>, 1.235 - or a character between U+0041 LATIN CAPITAL LETTER A (A) and U+0046 LATIN CAPITAL LETTER F (F), 1.236 + or a character between U+0041 LATIN CAPITAL LETTER A (A) and U+0046 LATIN CAPITAL LETTER F (F), 1.237 or a character between U+0061 LATIN SMALL LETTER A (a) and U+0066 LATIN SMALL LETTER F (f). 1.238 1.239 <dt><dfn>uppercase letter</dfn> 1.240 @@ -546,9 +546,9 @@ 1.241 1.242 <dt><dfn>newline</dfn> 1.243 <dd> 1.244 - U+000A LINE FEED or U+000C FORM FEED. 1.245 + U+000A LINE FEED or U+000C FORM FEED. 1.246 <span class='note'> 1.247 - Note that U+000D CARRIAGE RETURN is not included in this definition, 1.248 + Note that U+000D CARRIAGE RETURN is not included in this definition, 1.249 as it is removed from the stream during preprocessing. 1.250 </span> 1.251 1.252 @@ -728,7 +728,7 @@ 1.253 1.254 <dt>U+005C REVERSE SOLIDUS (\) 1.255 <dd> 1.256 - If the <i>next input character</i> is 1.257 + If the <i>next input character</i> is 1.258 a <i>newline</i> 1.259 or EOF, 1.260 this is a <i>parse error</i>. 1.261 @@ -974,7 +974,7 @@ 1.262 Reconsume the <i>current input character</i>. 1.263 1.264 <p> 1.265 - Otherwise, 1.266 + Otherwise, 1.267 <i>consume an escaped character</i>. 1.268 Create a hash token 1.269 with its value set to the returned character. 1.270 @@ -982,7 +982,7 @@ 1.271 1.272 <dt>anything else 1.273 <dd> 1.274 - Emit a delim token 1.275 + Emit a delim token 1.276 with its value set to U+0023 NUMBER SIGN (#). 1.277 Switch to the <i>data state</i>. 1.278 Reconsume the <i>current input character</i>. 1.279 @@ -1010,7 +1010,7 @@ 1.280 Reconsume the <i>current input character</i>. 1.281 1.282 <p> 1.283 - Otherwise, 1.284 + Otherwise, 1.285 <i>consume an escaped character</i>. 1.286 Append the returned character to the hash token's value. 1.287 Remain in this state. 1.288 @@ -1101,7 +1101,7 @@ 1.289 Reconsume the <i>current input character</i>. 1.290 1.291 <p> 1.292 - Otherwise, 1.293 + Otherwise, 1.294 <i>consume an escaped character</i>. 1.295 Create an at-keyword token 1.296 with its value set to the returned character. 1.297 @@ -1137,7 +1137,7 @@ 1.298 Reconsume the <i>current input character</i>. 1.299 1.300 <p> 1.301 - Otherwise, 1.302 + Otherwise, 1.303 <i>consume an escaped character</i>. 1.304 Append the returned character to the at-keyword token's value. 1.305 Remain in this state. 1.306 @@ -1177,7 +1177,7 @@ 1.307 1.308 <p> 1.309 Otherwise, 1.310 - emit a delim token 1.311 + emit a delim token 1.312 with its value set to U+002D HYPHEN-MINUS (-). 1.313 Switch to the <i>data state</i>. 1.314 1.315 @@ -1195,7 +1195,7 @@ 1.316 Reconsume the <i>current input character</i>. 1.317 1.318 <p> 1.319 - Otherwise, 1.320 + Otherwise, 1.321 <i>consume an escaped character</i>. 1.322 Create an ident token 1.323 with its value set to the returned character. 1.324 @@ -1205,7 +1205,7 @@ 1.325 This state should only be entered with a valid character. 1.326 If it hits anything else, this is a spec error. 1.327 --> 1.328 - 1.329 + 1.330 </dl> 1.331 1.332 <h4> 1.333 @@ -1230,14 +1230,14 @@ 1.334 Reconsume the <i>current input character</i>. 1.335 1.336 <p> 1.337 - Otherwise, 1.338 + Otherwise, 1.339 <i>consume an escaped character</i>. 1.340 Append the returned character to the ident token's value. 1.341 Remain in this state. 1.342 1.343 <dt>U+0028 LEFT PARENTHESIS (() 1.344 <dd> 1.345 - If the identifier token's value is 1.346 + If the identifier token's value is 1.347 an <i>ASCII case-insensitive</i> match for "url", 1.348 switch to the <i>url state</i>. 1.349 1.350 @@ -1734,11 +1734,11 @@ 1.351 1.352 <dt>anything else 1.353 <dd> 1.354 - Let <var>base</var> be the result of interpreting the portion of the number token's representation 1.355 + Let <var>base</var> be the result of interpreting the portion of the number token's representation 1.356 preceding the U+0045 LATIN CAPITAL LETTER E (E) or U+0065 LATIN SMALL LETTER E (e) 1.357 as a base-10 number. 1.358 <p> 1.359 - Let <var>power</var> be the result of interpreting the portion of the number token's representation 1.360 + Let <var>power</var> be the result of interpreting the portion of the number token's representation 1.361 following the U+0045 LATIN CAPITAL LETTER E (E) or U+0065 LATIN SMALL LETTER E (e) 1.362 as a base-10 number. 1.363 <p> 1.364 @@ -1969,7 +1969,7 @@ 1.365 Switch to the <i>bad-url state</i>. 1.366 1.367 <p> 1.368 - Otherwise, 1.369 + Otherwise, 1.370 <i>consume an escaped character</i>. 1.371 Append the returned character 1.372 to the url token's value. 1.373 @@ -2009,7 +2009,7 @@ 1.374 and remain in this state. 1.375 1.376 <p> 1.377 - Otherwise, 1.378 + Otherwise, 1.379 <i>consume an escaped character</i>. 1.380 Remain in this state. 1.381 1.382 @@ -2114,7 +2114,7 @@ 1.383 1.384 <p> 1.385 This section describes how to set a unicode-range token's range 1.386 - so that the range it describes 1.387 + so that the range it describes 1.388 is within the supported range of unicode characters. 1.389 1.390 <p> 1.391 @@ -2156,7 +2156,7 @@ 1.392 1.393 <p> 1.394 Here are the changes that I know that I've made to the tokenizer of 2.1. 1.395 - If there are changes not present here, 1.396 + If there are changes not present here, 1.397 please let me know 1.398 as they may be unintentional. 1.399 1.400 @@ -2192,7 +2192,7 @@ 1.401 The only consequence of this is that comments can no longer be inserted between the sign and the number. 1.402 1.403 <li> 1.404 - Some flags have been added for SVG-compatible tokenizing, 1.405 + Some flags have been added for SVG-compatible tokenizing, 1.406 so that a single state machine can be used for both "vanilla" and SVG CSS parsing. 1.407 1.408 <li> 1.409 @@ -2203,15 +2203,15 @@ 1.410 1.411 1.412 <!-- 1.413 -PPPPPPPPPPPPPPPPP AAA RRRRRRRRRRRRRRRRR SSSSSSSSSSSSSSS EEEEEEEEEEEEEEEEEEEEEERRRRRRRRRRRRRRRRR 1.414 -P::::::::::::::::P A:::A R::::::::::::::::R SS:::::::::::::::SE::::::::::::::::::::ER::::::::::::::::R 1.415 -P::::::PPPPPP:::::P A:::::A R::::::RRRRRR:::::R S:::::SSSSSS::::::SE::::::::::::::::::::ER::::::RRRRRR:::::R 1.416 +PPPPPPPPPPPPPPPPP AAA RRRRRRRRRRRRRRRRR SSSSSSSSSSSSSSS EEEEEEEEEEEEEEEEEEEEEERRRRRRRRRRRRRRRRR 1.417 +P::::::::::::::::P A:::A R::::::::::::::::R SS:::::::::::::::SE::::::::::::::::::::ER::::::::::::::::R 1.418 +P::::::PPPPPP:::::P A:::::A R::::::RRRRRR:::::R S:::::SSSSSS::::::SE::::::::::::::::::::ER::::::RRRRRR:::::R 1.419 PP:::::P P:::::P A:::::::A RR:::::R R:::::RS:::::S SSSSSSSEE::::::EEEEEEEEE::::ERR:::::R R:::::R 1.420 P::::P P:::::P A:::::::::A R::::R R:::::RS:::::S E:::::E EEEEEE R::::R R:::::R 1.421 P::::P P:::::PA:::::A:::::A R::::R R:::::RS:::::S E:::::E R::::R R:::::R 1.422 - P::::PPPPPP:::::PA:::::A A:::::A R::::RRRRRR:::::R S::::SSSS E::::::EEEEEEEEEE R::::RRRRRR:::::R 1.423 - P:::::::::::::PPA:::::A A:::::A R:::::::::::::RR SS::::::SSSSS E:::::::::::::::E R:::::::::::::RR 1.424 - P::::PPPPPPPPP A:::::A A:::::A R::::RRRRRR:::::R SSS::::::::SS E:::::::::::::::E R::::RRRRRR:::::R 1.425 + P::::PPPPPP:::::PA:::::A A:::::A R::::RRRRRR:::::R S::::SSSS E::::::EEEEEEEEEE R::::RRRRRR:::::R 1.426 + P:::::::::::::PPA:::::A A:::::A R:::::::::::::RR SS::::::SSSSS E:::::::::::::::E R:::::::::::::RR 1.427 + P::::PPPPPPPPP A:::::A A:::::A R::::RRRRRR:::::R SSS::::::::SS E:::::::::::::::E R::::RRRRRR:::::R 1.428 P::::P A:::::AAAAAAAAA:::::A R::::R R:::::R SSSSSS::::S E::::::EEEEEEEEEE R::::R R:::::R 1.429 P::::P A:::::::::::::::::::::A R::::R R:::::R S:::::S E:::::E R::::R R:::::R 1.430 P::::P A:::::AAAAAAAAAAAAA:::::A R::::R R:::::R S:::::S E:::::E EEEEEE R::::R R:::::R 1.431 @@ -2253,7 +2253,7 @@ 1.432 1.433 <dt><dfn>style rule</dfn> 1.434 <dd> 1.435 - A style rule has 1.436 + A style rule has 1.437 a selector consisting of a list of component values, 1.438 and a value consisting of a list of at-rules or declarations. 1.439 1.440 @@ -2377,8 +2377,8 @@ 1.441 1.442 <dt><dfn>stack of open rules</dfn> 1.443 <dd> 1.444 - A stack of rules. 1.445 - This stack always contains the stylesheet object at the bottom of the stack, 1.446 + A stack of rules. 1.447 + This stack always contains the stylesheet object at the bottom of the stack, 1.448 gains additional rules as block are opened, 1.449 and loses them when blocks are closed. 1.450 1.451 @@ -2537,7 +2537,7 @@ 1.452 <dd> 1.453 <i>Consume a component value</i>. 1.454 If anything was returned, 1.455 - append the returned value 1.456 + append the returned value 1.457 to the prelude of the <i>current rule</i>. 1.458 Remain in this mode. 1.459 1.460 @@ -2563,7 +2563,7 @@ 1.461 <dd> 1.462 Do nothing. 1.463 Remain in this mode. 1.464 - 1.465 + 1.466 <dt>} token 1.467 <dd> 1.468 <i>Pop the current rule</i>. 1.469 @@ -2610,7 +2610,7 @@ 1.470 <i>Reconsume the current input token</i>. 1.471 1.472 <p> 1.473 - Otherwise, 1.474 + Otherwise, 1.475 this is a <i>parse error</i>. 1.476 <i>Discard the current rule</i>. 1.477 <i>Switch to the current rule's content mode</i>. 1.478 @@ -2626,7 +2626,7 @@ 1.479 <dd> 1.480 <i>Consume a component value</i>. 1.481 If anything was returned, 1.482 - append the returned value 1.483 + append the returned value 1.484 to the selector of the <i>current rule</i>. 1.485 Remain in this mode. 1.486 1.487 @@ -2847,7 +2847,7 @@ 1.488 <dfn>Declaration-end mode</dfn></h4> 1.489 1.490 <!-- 1.491 - This is intended only for times 1.492 + This is intended only for times 1.493 when you've just consumed something that must come at the end of a declaration. 1.494 Currently, that's just !important. 1.495 --> 1.496 @@ -2900,7 +2900,7 @@ 1.497 1.498 <h4> 1.499 <dfn>Next-block error mode</dfn></h4> 1.500 - 1.501 + 1.502 <!-- Make sure you've already discarded the error'd rule before switching here! --> 1.503 1.504 <p> 1.505 @@ -2927,7 +2927,7 @@ 1.506 1.507 <h4> 1.508 <dfn>Next-declaration error mode</dfn></h4> 1.509 - 1.510 + 1.511 <!-- Make sure you've already unset the current declaration before switching here! --> 1.512 1.513 <p> 1.514 @@ -2966,7 +2966,7 @@ 1.515 1.516 <h4> 1.517 <dfn>Next-block-or-statement error mode</dfn></h4> 1.518 - 1.519 + 1.520 <!-- Make sure you've already discarded the error'd rule before switching here! --> 1.521 1.522 <p> 1.523 @@ -3054,7 +3054,7 @@ 1.524 </ul> 1.525 1.526 <p> 1.527 - If the <i>current input token</i> is a number token, 1.528 + If the <i>current input token</i> is a number token, 1.529 let <var>value</var> be the token's representation. 1.530 If the <i>current input token</i> is a dimension token, 1.531 let <var>value</var> be the token's representation followed by the token's unit. 1.532 @@ -3148,7 +3148,7 @@ 1.533 return the block. 1.534 1.535 <p> 1.536 - Otherwise, 1.537 + Otherwise, 1.538 return nothing. 1.539 1.540 <dt>anything else 1.541 @@ -3169,7 +3169,7 @@ 1.542 1.543 <p> 1.544 Create a function with a name equal to the value of the <i>current input token</i>. 1.545 - Create an argument, 1.546 + Create an argument, 1.547 called the <dfn>current argument</dfn>, 1.548 which is initially empty. 1.549 1.550 @@ -3305,7 +3305,7 @@ 1.551 1.552 <p class='issue'> 1.553 Here are the changes that I know that I've made to the Core Grammar of 2.1. 1.554 - If there are changes not present here, 1.555 + If there are changes not present here, 1.556 please let me know 1.557 as they may be unintentional. 1.558 1.559 @@ -3330,7 +3330,7 @@ 1.560 <ul> 1.561 <li> 1.562 [] blocks, () blocks and functions can now contain {} blocks, at-keywords or semicolons 1.563 - 1.564 + 1.565 <li> 1.566 Selectors can now contain semicolons 1.567 1.568 @@ -3352,14 +3352,14 @@ 1.569 1.570 <p> 1.571 All of the algorithms defined in this section begin in the parser. 1.572 - It is assumed that the <a href="#preprocessing-the-input-stream">input preprocessing</a> 1.573 + It is assumed that the <a href="#preprocessing-the-input-stream">input preprocessing</a> 1.574 and <a href="#tokenization">tokenization</a> 1.575 steps have already been completed, 1.576 resulting in a stream of tokens. 1.577 1.578 <div class='issue'> 1.579 <p> 1.580 - The following notes should probably be translated into normative text in the relevant specs, 1.581 + The following notes should probably be translated into normative text in the relevant specs, 1.582 hooking this spec's terms: 1.583 1.584 <ul> 1.585 @@ -3444,12 +3444,12 @@ 1.586 <ol> 1.587 <li> 1.588 Initialize the <i>stack of open rules</i> by pushing a new <i>stylesheet</i> onto it, 1.589 - and then pushing a new <i>style rule</i> onto it 1.590 + and then pushing a new <i>style rule</i> onto it 1.591 with a selector set to the empty string 1.592 and an initially empty value. 1.593 1.594 <li> 1.595 - Invoke the <a href="#parser-state-machine">parser</a>, 1.596 + Invoke the <a href="#parser-state-machine">parser</a>, 1.597 with the <i>only declarations</i> flag set, 1.598 starting in the <i>declaration-block mode</i>. 1.599 1.600 @@ -3565,7 +3565,7 @@ 1.601 <dt>dimension token 1.602 <dd> 1.603 Append the token's value, representation, or representation and unit, respectively, to <var>repr</var>. 1.604 - 1.605 + 1.606 <dt>delim token with the value "+" 1.607 <dd> 1.608 Append U+002B PLUS SIGN (+) to <var>repr</var>. 1.609 @@ -3607,7 +3607,7 @@ 1.610 1.611 <li> 1.612 Otherwise, if <var>repr</var> consists solely of <i>digits</i>, 1.613 - optionally prefixed with a single 1.614 + optionally prefixed with a single 1.615 U+002B PLUS SIGN (+) 1.616 or U+002D HYPHEN-MINUS (-), 1.617 interpret <var>repr</var> as a base-10 number, 1.618 @@ -3636,7 +3636,7 @@ 1.619 1.620 <li> 1.621 Otherwise, if the first string consists solely of <i>digits</i>, 1.622 - optionally prefixed with a single 1.623 + optionally prefixed with a single 1.624 U+002B PLUS SIGN (+) 1.625 or U+002D HYPHEN-MINUS (-), 1.626 interpret the first string as a base-10 number, 1.627 @@ -3658,7 +3658,7 @@ 1.628 <li> 1.629 Otherwise, if the second string consists solely of 1.630 0 or more U+0020 SPACE characters, 1.631 - optionally followed by a single 1.632 + optionally followed by a single 1.633 U+002B PLUS SIGN (+) 1.634 or U+002D HYPHEN-MINUS (-) character, 1.635 followed by 0 or more U+0020 SPACE characters, 1.636 @@ -3739,42 +3739,42 @@ 1.637 1.638 1.639 <!-- 1.640 - 1.641 + 1.642 TTTTTTTTTTTTTTTTTTTTTTTHHHHHHHHH HHHHHHHHHEEEEEEEEEEEEEEEEEEEEEE 1.643 T:::::::::::::::::::::TH:::::::H H:::::::HE::::::::::::::::::::E 1.644 T:::::::::::::::::::::TH:::::::H H:::::::HE::::::::::::::::::::E 1.645 T:::::TT:::::::TT:::::THH::::::H H::::::HHEE::::::EEEEEEEEE::::E 1.646 TTTTTT T:::::T TTTTTT H:::::H H:::::H E:::::E EEEEEE 1.647 - T:::::T H:::::H H:::::H E:::::E 1.648 - T:::::T H::::::HHHHH::::::H E::::::EEEEEEEEEE 1.649 - T:::::T H:::::::::::::::::H E:::::::::::::::E 1.650 - T:::::T H:::::::::::::::::H E:::::::::::::::E 1.651 - T:::::T H::::::HHHHH::::::H E::::::EEEEEEEEEE 1.652 - T:::::T H:::::H H:::::H E:::::E 1.653 + T:::::T H:::::H H:::::H E:::::E 1.654 + T:::::T H::::::HHHHH::::::H E::::::EEEEEEEEEE 1.655 + T:::::T H:::::::::::::::::H E:::::::::::::::E 1.656 + T:::::T H:::::::::::::::::H E:::::::::::::::E 1.657 + T:::::T H::::::HHHHH::::::H E::::::EEEEEEEEEE 1.658 + T:::::T H:::::H H:::::H E:::::E 1.659 T:::::T H:::::H H:::::H E:::::E EEEEEE 1.660 TT:::::::TT HH::::::H H::::::HHEE::::::EEEEEEEE:::::E 1.661 T:::::::::T H:::::::H H:::::::HE::::::::::::::::::::E 1.662 T:::::::::T H:::::::H H:::::::HE::::::::::::::::::::E 1.663 TTTTTTTTTTT HHHHHHHHH HHHHHHHHHEEEEEEEEEEEEEEEEEEEEEE 1.664 - 1.665 - 1.666 - 1.667 -EEEEEEEEEEEEEEEEEEEEEENNNNNNNN NNNNNNNNDDDDDDDDDDDDD 1.668 -E::::::::::::::::::::EN:::::::N N::::::ND::::::::::::DDD 1.669 -E::::::::::::::::::::EN::::::::N N::::::ND:::::::::::::::DD 1.670 -EE::::::EEEEEEEEE::::EN:::::::::N N::::::NDDD:::::DDDDD:::::D 1.671 - E:::::E EEEEEEN::::::::::N N::::::N D:::::D D:::::D 1.672 + 1.673 + 1.674 + 1.675 +EEEEEEEEEEEEEEEEEEEEEENNNNNNNN NNNNNNNNDDDDDDDDDDDDD 1.676 +E::::::::::::::::::::EN:::::::N N::::::ND::::::::::::DDD 1.677 +E::::::::::::::::::::EN::::::::N N::::::ND:::::::::::::::DD 1.678 +EE::::::EEEEEEEEE::::EN:::::::::N N::::::NDDD:::::DDDDD:::::D 1.679 + E:::::E EEEEEEN::::::::::N N::::::N D:::::D D:::::D 1.680 E:::::E N:::::::::::N N::::::N D:::::D D:::::D 1.681 E::::::EEEEEEEEEE N:::::::N::::N N::::::N D:::::D D:::::D 1.682 E:::::::::::::::E N::::::N N::::N N::::::N D:::::D D:::::D 1.683 E:::::::::::::::E N::::::N N::::N:::::::N D:::::D D:::::D 1.684 E::::::EEEEEEEEEE N::::::N N:::::::::::N D:::::D D:::::D 1.685 E:::::E N::::::N N::::::::::N D:::::D D:::::D 1.686 - E:::::E EEEEEEN::::::N N:::::::::N D:::::D D:::::D 1.687 -EE::::::EEEEEEEE:::::EN::::::N N::::::::NDDD:::::DDDDD:::::D 1.688 -E::::::::::::::::::::EN::::::N N:::::::ND:::::::::::::::DD 1.689 -E::::::::::::::::::::EN::::::N N::::::ND::::::::::::DDD 1.690 -EEEEEEEEEEEEEEEEEEEEEENNNNNNNN NNNNNNNDDDDDDDDDDDDD 1.691 + E:::::E EEEEEEN::::::N N:::::::::N D:::::D D:::::D 1.692 +EE::::::EEEEEEEE:::::EN::::::N N::::::::NDDD:::::DDDDD:::::D 1.693 +E::::::::::::::::::::EN::::::N N:::::::ND:::::::::::::::DD 1.694 +E::::::::::::::::::::EN::::::N N::::::ND::::::::::::DDD 1.695 +EEEEEEEEEEEEEEEEEEEEEENNNNNNNN NNNNNNNDDDDDDDDDDDDD 1.696 --> 1.697 1.698 <h2 id="conformance"> 1.699 @@ -3790,21 +3790,21 @@ 1.700 document are to be interpreted as described in RFC 2119. 1.701 However, for readability, these words do not appear in all uppercase 1.702 letters in this specification. 1.703 - 1.704 + 1.705 <p>All of the text of this specification is normative except sections 1.706 explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p> 1.707 - 1.708 + 1.709 <p>Examples in this specification are introduced with the words “for example” 1.710 or are set apart from the normative text with <code>class="example"</code>, 1.711 like this: 1.712 - 1.713 + 1.714 <div class="example"> 1.715 <p>This is an example of an informative example.</p> 1.716 </div> 1.717 - 1.718 + 1.719 <p>Informative notes begin with the word “Note” and are set apart from the 1.720 normative text with <code>class="note"</code>, like this: 1.721 - 1.722 + 1.723 <p class="note">Note, this is an informative note.</p> 1.724 1.725 <h3 id="conformance-classes"> 1.726 @@ -3824,13 +3824,13 @@ 1.727 <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a> 1.728 that writes a style sheet. 1.729 </dl> 1.730 - 1.731 + 1.732 <p>A style sheet is conformant to CSS Syntax Module Level 3 1.733 if it is syntactically valid according to this module. 1.734 - 1.735 + 1.736 <p>A renderer is conformant to CSS Syntax Module Level 3 1.737 if it parses a stylesheet according to this module. 1.738 - 1.739 + 1.740 <p>An authoring tool is conformant to CSS Syntax Module Level 3 1.741 if it writes style sheets that are syntactically valid according to this module. 1.742 1.743 @@ -3886,4 +3886,3 @@ 1.744 sgml-local-ecat-files:nil 1.745 End: 1.746 --> 1.747 -