- From: Eoghan Murray via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Mar 2022 15:17:05 +0000
- To: public-css-archive@w3.org
It's not impossible, the behaviour just needs to be written down in order for this to progress into the spec. @Loirooriol is pointing out that allowing `auto` to be passed to calc enabes the final (used) value to be calculated at layout time, so if that was supported the `auto` would be recalculated at each discreet transition step (thing requestAnimationFrame I guess?) In the absence of such a proposal (which is elegant and general, but I don't think anyone is clamouring or has worked out the edge cases), and also because the 'virtual layout' calculations could potentially be costly, would it be possible from a spec point of view to defer the implementation details to the browser: - browsers iniitally calculate a 'virtual' used value for `auto` at the start of the transition given current conditions - browsers _must_ recalculate `auto` at the end of the transition to ensure that the used value has not changed since the start of the transition - browser _may_ recalculate a used value for `auto` at each step of the transition for a smoother transition in the presence of other changes Is there precedence for this style of specification? Should we write up the various approaches in separate issues? @Loirooriol a stub of each of the competing possibilities that are in your head would be very helpful! -- GitHub Notification of comment by eoghanmurray Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/626#issuecomment-1055553437 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 15:17:06 UTC