- From: danegraphics via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Mar 2022 16:41:40 +0000
- To: public-css-archive@w3.org
I want to see if I can summarize what I'm understanding from this. Please correct me if I'm wrong. The main issue is that `auto` currently uses computed values instead of used/resolved values. If it were to use the used/resolved values for transitioning, then it would be able to be transitioned from and to with no issues, and it would even be able to be used in `calc()`. Is that correct? If so, then I think we can assume that this is a minimal increase in computation cost for the browsers because they are essentially already doing these calculations in a roundabout way anyway. And if that's the case, then no need to take half-measures. Just go full in and have it update on every transition step/frame. Browsers essentially already do this if elements surrounding an `auto` element are changing in size and space, and those are the only situations we're really worried about. Please correct me if I'm wrong, but assuming all this is true, then the changes to the spec that are needed are just to have browsers calculate and use a used/resolved value of `auto`, and then to just tell them to enable usage of `auto` in transitions and in `calc()`. -- GitHub Notification of comment by danegraphics Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/626#issuecomment-1055636543 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:41:41 UTC