Wed, 13 Feb 2013 18:26:41 -0800
[css3-syntax] Remove issue about lowercasing languaged-defined stuff. It'll be handled by serialization, per chatter at the last f2f.
css3-syntax/Overview.html | file | annotate | diff | comparison | revisions | |
css3-syntax/Overview.src.html | file | annotate | diff | comparison | revisions |
1.1 --- a/css3-syntax/Overview.html Wed Feb 13 18:24:48 2013 -0800 1.2 +++ b/css3-syntax/Overview.html Wed Feb 13 18:26:41 2013 -0800 1.3 @@ -641,13 +641,6 @@ 1.4 composed of one or more characters. Unicode-range tokens have a range of 1.5 characters. 1.6 1.7 - <p class=issue> Several types of tokens that are guaranteed to be 1.8 - language-defined, like at-keywords, functions, or dimension units, are 1.9 - always lowercased when serialized. Should we eagerly lowercase them in the 1.10 - parser, or leave that to serialization to deal with? (I slightly lean 1.11 - toward letting serialization deal with it, so we don't mess with the 1.12 - capitalization of variable values.) 1.13 - 1.14 <p> The tokenizer state machine consists of the states defined in the 1.15 following subsections. 1.16
2.1 --- a/css3-syntax/Overview.src.html Wed Feb 13 18:24:48 2013 -0800 2.2 +++ b/css3-syntax/Overview.src.html Wed Feb 13 18:26:41 2013 -0800 2.3 @@ -399,15 +399,6 @@ 2.4 Dimension tokens additionally have a unit composed of one or more characters. 2.5 Unicode-range tokens have a range of characters. 2.6 2.7 - <p class='issue'> 2.8 - Several types of tokens that are guaranteed to be language-defined, 2.9 - like at-keywords, functions, or dimension units, 2.10 - are always lowercased when serialized. 2.11 - Should we eagerly lowercase them in the parser, 2.12 - or leave that to serialization to deal with? 2.13 - (I slightly lean toward letting serialization deal with it, 2.14 - so we don't mess with the capitalization of variable values.) 2.15 - 2.16 <p> 2.17 The tokenizer state machine consists of the states defined in the following subsections. 2.18