- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Jan 2021 21:03:32 +0000
- To: public-css-archive@w3.org
To summarize the issue a bit (and revive the discussion): * We'd like to avoid doing animation work in content-visibility subtrees when they are not rendered * One approach is to avoid creating animations / ticking them / ending them when unrendered * However, if style is updated for any reason, the animation state is 'refreshed' * A problem with this is something like getAnimations({ subtree: true }) since that can force us to visit every node looking for nodes that had skipped style. For the last point, I'd like to not do that work and skip returning animations that are in content-visibility skipped subtrees. That seems a bit inconsistent with refreshing animation state if style is updated. Also, I'm not sure of potential use cases (i.e. is it important for us to return animations in content-visibility skipped subtrees when we ask for getAnimations with subtree: true?) -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5611#issuecomment-755692655 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 January 2021 21:03:35 UTC