- From: Sebastian Zartner via GitHub <noreply@w3.org>
- Date: Sun, 18 Jan 2026 21:54:17 +0000
- To: public-css-archive@w3.org
> That would prevent most caching and off main thread parsing optimizations, so I don't think that's a very appealing approach imho Finding a solution that keeps caching and parsing optimizations intact ‒ or generally speaking doesn't cause huge performance issues ‒ is one of the main aspects here. Though I want to point out that the polyfills discussed here already have to parse all the CSS via JS and possibly react to any changes to do that over and over again. So they do already have a huge performance impact. Therefore, any built-in solution we can come up with will surely have a positive impact on performance for such polyfills. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13186#issuecomment-3765786946 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 18 January 2026 21:54:17 UTC