- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Jan 2023 07:25:18 +0000
- To: public-css-archive@w3.org
> If you're producing some tooling that cares about that, you're going beyond what's specced, and are on your own. Correct :) Still doing my best not to invent too many things. > the reason urls and non-urls parse differently in this way is to retain the limited character lookahead In that case it makes sense for us to do more lookahead and "attribute" all the whitespace characters to the whitespace token. As you said this does not affect the actual token stream and wont affect parsing into component values. Thank you for these insights 🙇 -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8280#issuecomment-1370566921 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 4 January 2023 07:25:20 UTC