- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Nov 2023 17:26:34 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[view-transitions-1] Is view-transition-name discretely animatable?`, and agreed to the following: * `RESOLVED: v-t-name is discretely animatable.` <details><summary>The full IRC log of that discussion</summary> <fantasai> khush: question was about view-transition-name, currently discretely animatable<br> <flackr> q+<br> <fantasai> khush: but doesn't make much sense to be animatable<br> <fantasai> khush: feeds into pseudo-element DOM<br> <fantasai> khush: I would be OK making not animatable instead<br> <Rossen_> ack flackr<br> <fantasai> flackr: We've made this mistake on a few properties in the past, thought they shouldn't be animatable and then took compat risk to make not animatable later<br> <noamr> q+<br> <fantasai> flackr: if no strong technical reason to make them discretely animatable, would prefer to err on that side<br> <dbaron> s/not animatable later/animatable later/<br> <fantasai> khush: I don't have a strong opinion either way<br> <fantasai> khush: maybe we should wait for ntim<br> <Rossen_> ack noamr<br> <astearns> +1 to discrete animation as a default to use unless we have a good reason not to<br> <fantasai> noamr: There is a reason to make things discretely animatable for things not animatable, because ppl use animation-delay in various strange ways<br> <fantasai> noamr: e.g. "in 10s this property would change"<br> <fantasai> noamr: could be useful for view-transitions as well<br> <khush> q?<br> <khush> q+<br> <fantasai> Rossen_: we could resolve to keep discretely animatable, and if Tim has reasons to argue opposite, he can bring it back<br> <TabAtkins> ScribeNick: TabAtkins<br> <Rossen_> ack fantasai<br> <TabAtkins> fantasai: What does it mean to change VT-name halfway thru an animation?<br> <fantasai> noamr: for regular keyframe animations, at 50% view-transition-name changes<br> <fantasai> noamr: view-transition animation itself doesn't change it<br> <TabAtkins> fantasai: So you're saying that vt-name isn't animated during a VT, but can be during a regular animation<br> <TabAtkins> fantasai: IN which case the value fo the property gets captured at its current animated state if you trigger a VT during the animation<br> <TabAtkins> noamr: Yes. And that could be, like, an animation-delay just to timeout a change<br> <fantasai> noamr: people use that for timeouts sometimes<br> <Rossen_> ack khush<br> <TabAtkins> khush: It soundsl ike the reason we want it to be discrete animatable isn't a VT issue, just CSS in general.<br> <fantasai> khush: wanted to add was, keeping it discretely animatable has nothing to do with view transitions<br> <fantasai> khush: but general CSS<br> <fantasai> khush: We could add a note to [missed]<br> <flackr> https://www.w3.org/TR/web-animations/#not-animatable<br> <TabAtkins> khush: Coudl we add a note to Animation telling spec authors to make the property discrete unless there's a good reason?<br> <TabAtkins> flackr: The first note there explains when props *should* be excluded from animation<br> <Rossen_> q?<br> <TabAtkins> Rossen_: So convo leads me to ask for resolution, to keep as discretely animatable. Objections?<br> <TabAtkins> fantasai: I think given it doesn't affect VT animation it's probabkly fine.<br> <TabAtkins> fantasai: We can go back to Tim and check with him<br> <TabAtkins> Rossen_: Right, there's agreement on the call and if Tim feels strongly we can bring it back up<br> <TabAtkins> RESOLVED: v-t-name is discretely animatable.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9619#issuecomment-1823193469 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 November 2023 17:26:36 UTC