- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jul 2023 19:41:46 +0000
- To: public-css-archive@w3.org
> Doesn't seem much likely to happen due to https://github.com/w3c/csswg-drafts/issues/1026#issuecomment-341295647 Could something akin to setting up a particular scope for a certain counter help with that? Similar to how we can use `timeline-scope` to set up a scope for an animation? So something like a `counter-value-scope: foo` on a container switching anything that tries to access this particular counter's value inside to this non-parallel/delayed slower mode? This way nothing would be affected by default, and authors couldn't easily “break” the performance of everything, as they would be required to explicitly state which counter should receive this behavior. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1026#issuecomment-1633107722 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 July 2023 19:41:47 UTC