- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Wed, 08 Apr 2026 20:41:04 +0000
- To: public-css-archive@w3.org
Charset is problematic because it's a bizarre misfeature in the first place. Having a document declare its own encoding *in* that encoding is already weird and fragile, but if you want to do it, you need that info as fast as possible so you're not forced to hang onto the entire bytestream *just in case* you end up needing to reinterpret it. This one, on the other hand, only has an effect on layout. We simply don't *need* to know it before `head` is parsed in ~100% of cases (nobody, in practice, ever causes `head` to be displayed). Can you elaborate on any actual issues with doing it this way, for such a late-mattering decision that doesn't affect how the document itself is handled? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1771#issuecomment-4209509205 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 April 2026 20:41:05 UTC