- From: Hermann Stanew via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Feb 2025 04:08:17 +0000
- To: public-css-archive@w3.org
> I would go as far as to say that we would be better off going with the solution recommended in [this article](https://blog.dwac.dev/posts/html-whitespace/#how-could-we-fix-this), but making it compatible with older HTML versions by simply having to go from `<!doctype html>` to `<!doctype html quoted>` or `<!doctype html-quoted>` or `<!doctype html-q>` or `<!doctype htmlq>` or something like that, which to to tell the renderers how to treat the text inside the document. > > Unfortunately, I doubt this solution would be implemented, even though it would make using and and debugging things which involve HTML and CSS, much easier. @sapioit you are **insane** if you believe this is reason enough to touch `<!DOCTYPE>`. the most likely scenario in which `<!DOCTYPE>` is patched, would be MDN and WHATWG joining into the HTML6 community: `<!DOCTYPE html6>`, and nothing else comes close. i encourage the public paritcipation from common developers in spec authorship. **but copy pasting opinions from entertainment-coding-youtube-channels, is not how you do it.** [this is the video in question](https://www.youtube.com/watch?v=qF7iXBk1s5o) and the reason why this issue is getting so much traction. -- GitHub Notification of comment by junaga Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10821#issuecomment-2664561709 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 February 2025 04:08:18 UTC