- From: Jason Gronn via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Nov 2022 19:07:08 +0000
- To: public-css-archive@w3.org
> > **Note:** The tokens `<}-token>`s, `<)-token>`s, `<]-token>`, `<bad-string-token>`, and `<bad-url-token>` are always parse errors, , but they are preserved in the token stream by this specification to allow other specs, such as Media Queries, to define more fine-grained error-handling than just dropping an entire declaration or block > > This may explain why no parse error is "emitted" in _consume a URL token_ but it is not clear to me as well. If this is the case, then it would mean that the spec is inconsistent. In some spec slightly below it, a parse error is "emitted" as well as a bad-url-token being returned.  -- GitHub Notification of comment by JasonTheKitten Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7987#issuecomment-1298983080 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 November 2022 19:07:10 UTC