19484 2012-10-11 21:12:07 +0000 Inconsistency in regards to EOF (and EOF token) 2012-10-11 21:12:07 +0000 1 1 1 Unclassified CSS Syntax unspecified PC Linux NEW P2 normal --- 1 bfrohs jackalmage public-css-bugzilla oldest_to_newest 76034 0 bfrohs 2012-10-11 21:12:07 +0000 In the "Data state", an "end-of-file token" is emitted: > EOF > Emit an end-of-file token. In the Tree Construction Definitions, an "EOF token" is mentioned: > next input token > The token following the current input token in the list of tokens produced by the tokenizer. If there isn't a token following the current input token, the next input token is an *EOF token*. In the "Top-level mode", "At-rule-prelude mode", "Rule-block mode", and several other modes, an "EOF token" is expected. E.g.: > EOF token > Finish parsing. However, neither "EOF token" or "end-of-file token" is mentioned in the list of possible tokens in the Tokenization overview: > The output of the tokenization step is a series of zero or more of the following tokens: identifier, function, at-keyword, hash, string, bad-string, url, bad-url, delim, number, percentage, dimension, unicode-range, whitespace, comment, cdo, cdc, colon, semicolon, [, ], (, ), {, }.