- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 Aug 2022 16:15:39 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `API for phase-linked offsets in keyframes`, and agreed to the following: * `RESOLVED: Use same object as in 7589 to specify keyframe offsets as well` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: API for phase-linked offsets in keyframes<br> <TabAtkins> github: https://github.com/w3c/csswg-drafts/issues/7637<br> <TabAtkins> flackr: Related to previous, we also resolved in CSS that you could link keyframes to timeline phases<br> <TabAtkins> flackr: But again we didn't have a JS way to do it<br> <TabAtkins> flackr: So the issue suggests that we reuse the previous resolution's format for specifying keyframe offsets<br> <TabAtkins> +1<br> <TabAtkins> flackr: So represetning a keyframe position as phase+offset<br> <TabAtkins> Rossen_: objections?<br> <bramus> +1<br> <Sebo> +1<br> <TabAtkins> flackr: Summarized: support passing a phase+offset object in the keyframe offsets<br> <TabAtkins> RESOLVED: Use same object as in 7589 to specify keyframe offsets as well<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7637#issuecomment-1233146537 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 August 2022 16:15:40 UTC