- From: Simon Sapin via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Apr 2020 16:12:01 +0000
- To: public-css-archive@w3.org
> I'd suggest linking the word parse in step 1 of [parse a selector](https://drafts.csswg.org/selectors-4/#parse-selector) (and [parse a relative selector](https://drafts.csswg.org/selectors-4/#parse-relative-selector)) to some algorithm which feeds a string as the input stream into the tokenizer, then into the grammar. They both link to specific rules inside the grammar at https://drafts.csswg.org/selectors-4/#grammar. That section starts with: > Selectors are [parsed](https://drafts.csswg.org/css-syntax-3/#css-parse-something-according-to-a-css-grammar) according to the following grammar: Which links to https://drafts.csswg.org/css-syntax-3/#css-parse-something-according-to-a-css-grammar which is ultimately based on the tokenizer. Perhaps it should be clearer that https://drafts.csswg.org/css-syntax-3/#input-preprocessing is a required step at some point, CC @tabatkins -- GitHub Notification of comment by SimonSapin Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4927#issuecomment-610479704 using your GitHub account
Received on Tuesday, 7 April 2020 16:12:03 UTC