|
11 | 11 |
|
12 | 12 | <meta content="CSS Syntax Module Level 3 (CSS3 Syntax)" name=dcterms.title> |
13 | 13 | <meta content=text name=dcterms.type> |
14 | | - <meta content=2013-02-15 name=dcterms.issued> |
| 14 | + <meta content=2013-02-18 name=dcterms.issued> |
15 | 15 | <meta content="http://dev.w3.org/csswg/css3-syntax/" name=dcterms.creator> |
16 | 16 | <meta content=W3C name=dcterms.publisher> |
17 | 17 | <meta content="http://dev.w3.org/csswg/css3-syntax/" |
|
31 | 31 |
|
32 | 32 | <h1>CSS Syntax Module Level 3</h1> |
33 | 33 |
|
34 | | - <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 15 February |
| 34 | + <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 18 February |
35 | 35 | 2013</h2> |
36 | 36 |
|
37 | 37 | <dl> |
@@ -489,7 +489,7 @@ <h2 id=syntax-description><span class=secno>2. </span> Description of CSS's |
489 | 489 | <h2 id=tokenizing-and-parsing-css><span class=secno>3. </span> Tokenizing |
490 | 490 | and Parsing CSS</h2> |
491 | 491 |
|
492 | | - <p> User agents must use the parsing rules described in this specifiction |
| 492 | + <p> User agents must use the parsing rules described in this specification |
493 | 493 | to generate the CSSOM trees from text/css resources. Together, these rules |
494 | 494 | define what is referred to as the CSS parser. |
495 | 495 |
|
@@ -587,7 +587,7 @@ <h3 id=the-input-byte-stream><span class=secno>3.2. </span> The input byte |
587 | 587 | the byte order mark (BOM) take precedence, hence the usage of the term |
588 | 588 | "fallback" above. |
589 | 589 |
|
590 | | - <p class=issue> Anne says that steps 4/5 should be an input to this |
| 590 | + <p class=issue> Anne says that steps 3/4 should be an input to this |
591 | 591 | algorithm from the specs that define importing stylesheet, to make the |
592 | 592 | algorithm as a whole cleaner. Perhaps abstract it into the concept of an |
593 | 593 | "environment charset" or something? |
|
0 commit comments