- From: danegraphics via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Feb 2022 16:39:54 +0000
- To: public-css-archive@w3.org
@Loirooriol > Resolving it as a length needs layout, at computed-value time it's too early. Then we should resolve it as a length. When we are talking about the "computed" value of `auto`, we are talking about the final pixel/length value of the layout with `auto` applied. Essentially, we want to calculate and transition to an equivalent final value, and then replace that with `auto` when the transition finishes. We do not care about any values that do not result in the final layout resulting from using `auto`. And if the final value of `auto` changes during the transition, we would simply rather ignore it. In the overwhelming majority of cases, it will not change during the transition. And the few cases where it does change during transition will be cases where it is okay if it snaps to the new value afterward. -- GitHub Notification of comment by danegraphics Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/626#issuecomment-1054445751 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 February 2022 16:39:56 UTC