- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Feb 2022 23:08:05 +0000
- To: public-css-archive@w3.org
> 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 right entry point to use. Both of these are potential entry points, and so they both need normalization. It is indeed the case that if you're starting from "parse according to a grammar", you don't need to repeat that normalization when calling into "parse a list of component values", but that's just a possible optimization step; once the input has been normalized, attempting to normalize it again is a no-op. > It is not strictly related, I think (I will open a new issue if required) Yes, please open this as a new issue; it's a separate topic about a different spec, and so bringing it up in an already-closed issue about something unrelated means it's gonna be lost. (Luckily I spotted this when I was closing a bunch of open tabs.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4927#issuecomment-1029484391 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 February 2022 23:08:07 UTC