- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Jan 2025 23:37:14 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[scroll-animations-1] Allow `<length-percentage>` in `<keyframe-selector>` when combined with `<timeline-range-name>` ``, and agreed to the following: * ``RESOLVED: Allow `<length-percentage>` in keyframe selectors (with or without `<timeline-range-name>`)`` <details><summary>The full IRC log of that discussion</summary> <emilio> bramus: this is about the syntax in the keyframe selector (currently `<percentage>` and `<timeline-range-name>`<br> <emilio> *)<br> <emilio> ... But in CSS you can specify `animation-range: entry calc(0% + 100px)`<br> <emilio> ... problem is this is not allowed in keyframes<br> <emilio> ... you can attach an animation to specified range that uses calc()<br> <emilio> ... if you have keyframes that contains ranges<br> <emilio> ... you can't<br> <emilio> ... so inside `@keyframes { cover 0% { ... } }`, but you can't do `@keyframes { cover calc(...) { ... } }`<br> <emilio> ... proposal is to change the syntax from percentage when timeline range name to also accept `<length-percentage>`<br> <emilio> ... so that you can choose to attach one animation or keyframes with predefine range info<br> <emilio> q+<br> <astearns> ack emilio<br> <emilio> emilio: what happens if the keyframe containing pixels is attached to the doc timeline (time based)<br> <emilio> bramus: I believe they get ignored<br> <emilio> emilio: seems fine I guess<br> <bramus> emilio: seems fine<br> <TabAtkins> emilio: seems fine<br> <bramus> emilio: seems consistent with previous issue rsolution<br> <bramus> … as long as its well defined when it does not apply<br> <bramus> bramus: that is already covered<br> <emilio> PROPOSED: Allow `<length-percentage>` in keyframe selectors<br> <emilio> bramus: not exactly<br> <emilio> ... bigger than what I asked but could work<br> <emilio> emilio: so you only wanted where you already have a range name<br> <emilio> bramus: right<br> <ydaniv> q+<br> <emilio> emilio: but on the previous issue we resolved that we want math functions there so allowing this seems consistent with that<br> <bramus> `<keyframe-selector> = from | to | <length-percentage> | <timeline-range-name> <length-percentage>`<br> <flackr> In the future, could do something like calc(50% + 1s)<br> <bramus> bramus: so this would be the syntax then ^<br> <astearns> ack ydaniv<br> <emilio> ydaniv: in order to make this apply to scroll timeline you also need plain `<length-percentage>`<br> <bramus> bramus: not really, as we have scroll range now<br> <emilio> bramus: not really because we decided to add the scroll range to scroll-timeline<br> <emilio> ... but would be nice<br> <astearns> bramus: not really<br> <bramus> emilio: seems ok<br> <kizu> +1<br> <emilio> PROPOSED: Allow `<length-percentage>` in keyframe selectors (with or without `<timeline-range-name>`)<br> <emilio> RESOLVED: Allow `<length-percentage>` in keyframe selectors (with or without `<timeline-range-name>`)<br> <emilio> fantasai: what about time based anims?<br> <emilio> emilio: get ignored apparently<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10000#issuecomment-2628570735 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 31 January 2025 23:37:14 UTC