- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 23 Jul 2025 16:49:22 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-view-transitions-2] Animating view-transition-group-children captures`, and agreed to the following: * `RESOLVED: animate the v-t-g-c border properties in the same way we animate other captured props` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> vmpstr: so we recently resolved to copy over border-radius and corner-shape<br> <TabAtkins> vmpstr: border-width is currently copied as a static value form the "old" element<br> <TabAtkins> vmpstr: for other props, we set up a from keyframe with the old values, and reflect the new values in the element's style, so you have an animation that runs from the old to the new, if they change between the two states<br> <TabAtkins> vmpstr: proposal is to do the same with the border properties on the group-children<br> <TabAtkins> vmpstr: want to point out, this doesn't perfectly match the visuals the user will see. the old capture cross-fades in to the new one.<br> <TabAtkins> vmpstr: so if you have a different width border you'll see a crossfade of the two borders. but the clip will animate, so if children are clipped it'll animate. it's close but not perfect, but still an improvement<br> <TabAtkins> astearns: do you have a conception of the ideal future state, and is this a step towards it?<br> <TabAtkins> vmpstr: there is... the ideal state a thing we called layered capture, where the new pseudos would only capture the contents, not the box decorations, and the box decos would animate on the pseudos instead. so this is a step in that direction.<br> <TabAtkins> vmpstr: we've tried to impl that model, it has a lot of complications. but it probably is ideal<br> <TabAtkins> astearns: summarize?<br> <TabAtkins> vmpstr: animate the v-t-g-c border properties in the same way we animate other captured props<br> <TabAtkins> astearns: concerns? anyone who wants more time?<br> <TabAtkins> ntim: is this only for the new group-children, or for all captures?<br> <TabAtkins> vmpstr: just for the new element<br> <TabAtkins> ntim: only for nested, or for all?<br> <TabAtkins> vmpstr: this element is only added for nested<br> <TabAtkins> ntim: sounds good<br> <TabAtkins> astearns: objections?<br> <TabAtkins> RESOLVED: animate the v-t-g-c border properties in the same way we animate other captured props<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12363#issuecomment-3109400630 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 July 2025 16:49:23 UTC