- From: Katie Roberts via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Feb 2025 18:10:19 +0000
- To: public-css-archive@w3.org
@dgp1130 going off of @sapioit 's comment, I like that idea better, but I am confused as to why [Newlines [would be] banned by default [in this new html syntax and] a quoted newline [would be flagged as a] syntax error.](https://blog.dwac.dev/posts/html-whitespace/#how-could-we-fix-this:~:text=Newlines%20are%20banned%20by%20default%20as%20it%20would%20be%20way%20too%20easy%20to%20forget%20a%20closing%20quote%20and%20introduce%20unintended%20significant%20spacing.%20Therefore%2C%20a%20quoted%20newline%20is%20a%20syntax%20error.) You say it is because it would be easier to forget closing quotes? and that using &lf; would be the replacement for /n in single quoted strings? (remember that some type of newline character is needed in single quoted strings, otherwise we would have to use a #define or something in cshtml to continually refer to a triple quoted newline string when creating strings programmatically) Is there some reason you chose &lf;? Does not quoting it produce errors more reliably than not quoting a /n? Is missing a closing quote that hard to debug? -- GitHub Notification of comment by rober423 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10821#issuecomment-2657377072 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 February 2025 18:10:20 UTC