- From: Jake Archibald via GitHub <noreply@w3.org>
- Date: Mon, 16 Feb 2026 19:41:16 +0000
- To: public-css-archive@w3.org
@bramus (I know I said this on bsky, but for the thread…) I don't understand the claim that it's "riddling content". Creating DOM ranges for CSS highlights is adding things to the DOM. It may not feel like it, because they're not in the elements panel, but they're there - that's how CSS highlights work. Someone will point out that their invisibility is a debugging issue, and they'll be revealed by devtools somehow. Yes, these markers will make the content of the `<pre>` harder to read by a human, but updating the text parts is easy once you find them. Your highlight map introduces machine-readable content into the markup, so the stuff in the `<pre>` is no longer human editable (unless they manually update the highlight map). Editing one without the other will introduce breakage. I'm not saying your idea is bad, just that it doesn't seem clearly better - it's a trade-off. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13381#issuecomment-3910262208 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 16 February 2026 19:41:17 UTC