- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Sep 2022 21:23:48 +0000
- To: public-css-archive@w3.org
What is the practical difference between this proposal and just using a class? The "performance issues" with changing the DOM are related to invalidating styles for affected elements, which would be *exactly* the same with this, yeah? (And, unless this is internally implemented using the same descendant-caching optimizations that classes currently use, the invalidation cost will be *worse* than just modifying classes.) Highlights needed a special mechanism because they don't exist in the DOM at all, so we needed to invent something outside of it to refer to them. But that just isn't the case here. Is there another issue with modifying classes that I'm missing? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7679#issuecomment-1239904842 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 September 2022 21:23:50 UTC