- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Feb 2019 23:50:17 +0000
- To: public-css-archive@w3.org
tabatkins has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-syntax] problem with parse component value == (migrated from mailing list) **Johannes Koch said:** > I think there is a problem with parsing a component value (5.3.6) in the CR. > > 4. Reconsume the current input token. Consume a component value and let > value be the return value. If nothing is returned, return a syntax error. > > 5. While the current input token is a `<whitespace-token>`, consume the > next input token. > > 6. If the current input token is an `<EOF-token>`, return value. > Otherwise, return a syntax error. > > We need to consume the next input token before step 5. Otherwise at step > 5, the current input token is the last token of the component value > consumed by 5.4.6. and cannot be either whitespace or EOF. ----------------- **Tab Atkins said:** > Ooh, very good catch. Fixed. (Rather than consuming the next token > eagerly, I just changed the condition to look at the next input > token.) > > I'm also not sure why I wrote the first couple of steps so awkwardly. > I've instead change them as well to look at the next input token, > rather than eagerly consuming, looking at current, then reconsuming. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3634 using your GitHub account
Received on Thursday, 7 February 2019 23:50:19 UTC