[csswg-drafts] [css-syntax] problem with parse rule (#3633)

tabatkins has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-syntax] problem with parse rule ==
(migrated from mailing list)

**Johannes Koch said:**

> There's a similar issue in 5.3.3. Parse a rule
> 
> 3. If the current input token is an `<EOF-token>`, return a syntax error.
> 
>     Otherwise, if the current input token is an `<at-keyword-token>`,
>     consume an at-rule and let rule be the return value.
> 
>     Otherwise, consume a qualified rule and let rule be the return
>     value. If nothing was returned, return a syntax error.
> 
> 4. While the current input token is a `<whitespace-token>`, consume the
>     next input token.
> 
> At step 4 the current input token is the last token consumed by 5.4.2. 
> or 5.4.3. ('}' or ';') and cannot be either whitespace or EOF.

---------------

**Tab Atkins said:**

> Ugh, sorry about that.  Fixed now.
> 
> I just reviewed all the other parse/consume algos as well, and found a
> few more current/next token bugs. They're all fixed, and I took the
> opportunity to make the spec algos more consistent - they now all
> operate on the remaining stream, ignoring the current input token, and
> several algorithms subsequently reconsume more often.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3633 using your GitHub account

Received on Thursday, 7 February 2019 23:47:40 UTC