- From: vmpstr via GitHub <noreply@w3.org>
- Date: Tue, 21 Jul 2026 14:02:12 +0000
- To: public-css-archive@w3.org
One hiccup here is the ability to have a meaningful size remembered. From https://drafts.csswg.org/css-sizing-4/#last-remembered: > The [auto](https://drafts.csswg.org/css-sizing-4/#valdef-contain-intrinsic-width-auto) keyword of contain-intrinsic-size allows a middle-ground: if an element is ever not [size-contained](https://drafts.csswg.org/css-contain-2/#size-containment), this value causes the element to remember its size (calculated as normal by layout); then, if the element gains size containment later, it will use the remembered size, offering the performance benefits of size containment while probably sizing accurately to its contents. The problem is that we apply `contain-intrinsic-size: auto` at the same time as we apply `contain: size`, so there is never a time when an element has one but not the other. I'm happy to do a carveout here and say that when we enter this mode, we set the last remembered size to whatever the current dimensions of the element are. This would be extra magic. @emilio are you OK with this? Also, from my testing it's somewhat important to run these steps https://drafts.csswg.org/css-view-transitions-2/#capture-the-old-state without size containment since some of it captures sizes and other things. So I can be precise with the timing in the PR if I figure out how this can be implemented. -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13428#issuecomment-5034989140 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 July 2026 14:02:13 UTC