- From: Jason Gronn via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Oct 2022 16:27:01 +0000
- To: public-css-archive@w3.org
JasonTheKitten has just created a new issue for https://github.com/w3c/csswg-drafts: == Potentially missing a "parse error" specifier in "consume a URL token"? == * please tag the issue title with the spec's shortname, like `[css-foo]` (this is the name from the spec URL, without a level number unless the issue is specific to that level). If you're proposing a new feature that doesn't obviously fit in an existing spec, skip this part — don't make something up. [css-syntax-3] * please be specific (in the title and issue) about what you want to change: “make it better” means different things to different people! The specification has a paragraph that is as follows: ![image](https://user-images.githubusercontent.com/15697938/199056487-b401e190-f084-4c02-a78e-eddd135ea8cd.png) 1) If the next input code point is \u0029, we are successful and return the URL token 2) If we have reached the end-of-file, we record a parse error and return the URL token 3) Otherwise, we consume the remnants and return a bad URL token In the third case, we have obviously run into poor, malformed syntax. However, the spec never actually says that a parse error is given in this case, so a spec-compliant validator would not actually report a problem. This leads me to think that we are missing a parse error. (Note: there is a parse error defined for the second case, but the way the spec is worded it does not apply to the third case) * please link to the spec section you're talking about, or at least the spec [CSS Syntax Module Level 3](https://www.w3.org/TR/css-syntax-3/#consume-url-token) Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7987 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 31 October 2022 16:27:02 UTC