- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Sat, 12 Aug 2023 11:41:32 +0000
- To: public-css-archive@w3.org
Ah ok, thanks. I would be happy if it was defined that when parsing a grammar, there is no guarantee that the input does not come with a leading or a trailing whitespace. Or if they were always consumed (in *consume an at-rule* and *consume a list of component values*) before parsing a grammar. Currently they seems to be consumed only in *consume a declaration*, not for `CSSStyleDeclaration.setProperty(property, value)` or `CSS.supports(property, value)`, which I think makes a difference for custom property values and property values containing an arbitrary substition value, when they include a leading or trailing comment. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9173#issuecomment-1675868315 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 12 August 2023 11:41:34 UTC