W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2021

Re: [csswg-drafts] [css-contain-3][css-animations][css-transitions] Isolate animation side-effects? (#6398)

From: andruud via GitHub <sysbot+gh@w3.org>
Date: Tue, 24 Aug 2021 21:10:03 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-904979009-1629839402-sysbot+gh@w3.org>
> How are container units defined? I would have thought that they would be similar to percentages, viewport units or calc where the computed value is a calc that does not itself change when the input variables change.

The only thing that "survives" to used-value time, is %. Everything else, including viewport units and container units are resolved to px at computed-value time, or sooner.

But yes, specifying that container units are resolved used-value time would probably be the way to "fix" the problem, if we were to define this as a problem.

> in the revised proposal it does include some animation effects

Yeah, agree. Should be more specific than "animation effects". Perhaps:

- Let the base style be the style as it would be without any declarations from the "animation" and "transition" origins, inheriting from the base style of the parent.

And then "animation effects" can still sneak its way into the base, since an animating container _can_ affect the author/user origin of descendants.

GitHub Notification of comment by andruud
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6398#issuecomment-904979009 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 24 August 2021 21:10:05 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:42 UTC