- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Mar 2022 16:23:29 +0000
- To: public-css-archive@w3.org
@SetTrend If `auto` is interpolated as a computed value, then e.g. at 50% of the transition it will be `calc(5em + auto/2)`, so you should get the same as if `div.outer` has no transition and `height: calc(5em + auto/2)`, when `div.inner` is as big as whatever size it has at that point during its transition. The exact behavior depends on how `auto` is handled in `calc()`, but probably this implies that the element would need to be laid out twice per frame, first with `height: auto`, and then with `calc()` replacing `auto` with the previous result. With the idea to interpolation used values, all of this should be properly designed. And again, I'm not an expert in this. If we are interpolating from `auto`, then we just take the old used value which is an absolute length and roughly, everything seems fine. If we are interpolating to `auto`, then it's less clear what should happen, like what's the computed value, etc. @eoghanmurray `auto` is always calculated at layout time. And again, the current interpolation model is based on computed values. If instead of interpolating `auto` itself, you try to resolve it first and interpolate that instead, then it's a different model that needs a proper design. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/626#issuecomment-1055619760 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 March 2022 16:23:30 UTC