- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Jan 2022 13:16:16 +0000
- To: public-css-archive@w3.org
> I also rewrote the parsing algos to explicitly put the input normalization into their algo steps, rather than relying on a blanket instruction for how to do normalization at the beginning of the section Step 1 of *parse something according to a CSS grammar* is now the input normalization but step 2, *parse a list of component values*, already has input normalization as its step 1. I do not know if this redundancy is for making things clearer. I'm just giving a feedback after looking for the expected entry point I was looking for. It is not strictly related, I think (I will open a new issue if required), but [parse a CSS value](https://drafts.csswg.org/cssom/#parsing-css-values) is: > 1. Let `list` be the value returned by invoking *parse a list of component values* from `value`. > 2. Match `list` against the grammar for the property `property` in the CSS specification. > [...] And I think it could it be simplified to the following: > 1. [Parse](https://drafts.csswg.org/css-syntax-3/#parse-grammar) `list` against the grammar for the property `property` in the CSS specification. > [...] -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4927#issuecomment-1012127022 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 January 2022 13:16:17 UTC