- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 25 Jun 2025 17:00:41 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[view-transitions-1] Have the `-image-pair`, `-old`, and `-new` pseudos inherit `animation-timing-function` ``, and agreed to the following: * `RESOLVED: Make animation-timing-function, -iteration-count, -direction, -play-state inherit in the VT tree` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> fantasai: We inherit some of the animation properties thru the VT tree, so you only have to specify it on -group<br> <TabAtkins> fantasai: so they'll all sync up their animations<br> <TabAtkins> fantasai: Bramus brought up that animation-timing-function should also inherit for the same reason.<br> <TabAtkins> fantasai: makes sense to me<br> <flackr> +1 sgtm<br> <TabAtkins> astearns: looks like Vlad wasn't sure about inheriting *everything*, but a-t-f made sense to them<br> <TabAtkins> fantasai: also mentioned were iteration-count and play-state. flackr probably has an idea of whether those make sense<br> <TabAtkins> fantasai: and direction<br> <TabAtkins> astearns: should we resolve on all four, or just the timing function?<br> <TabAtkins> flackr: maybe it makes sense to inherit all of them on VT, since they're related<br> <TabAtkins> flackr: i'd support all four, if we find one doesn't make sense we can revisit<br> <TabAtkins> PROPOSED: Make animation-timing-function, -iteration-count, -direction, -play-state inherit in the VT tree<br> <TabAtkins> astearns: objections?<br> <TabAtkins> RESOLVED: Make animation-timing-function, -iteration-count, -direction, -play-state inherit in the VT tree<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11546#issuecomment-3005503138 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 June 2025 17:00:42 UTC