- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Feb 2023 17:10:59 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[web-animations-2] Web animations API for specifying timeline phases in animation options.`, and agreed to the following: * `RESOLVED: take the api shape int he linked comments and add properties to the animation interface along timeline` <details><summary>The full IRC log of that discussion</summary> <argyle> astearns: first is about timeline phases, assuming rob is going tot ake this one<br> <argyle> flackr: lemme make things nice and simple..<br> <flackr> Proposed resolution in https://github.com/w3c/csswg-drafts/issues/7589#issuecomment-1380842759<br> <argyle> flackr: there's a proposed resolution int eh comment i linked<br> <ydaniv> s/int eh/in the/<br> <argyle> flackr: this isadding the ability to the web animations API to specify ranged names and offsets whciih we have already specced for css animations<br> <argyle> flackr: brian has looked at this proposed and agrees with the current designb, seems fine to add this to the animation options alongside the timeline attribute<br> <argyle> flackr: this shoudl allow us to control the same thhings from javascript animations<br> <argyle> flackr: any objections to the proposal?<br> <argyle> astearns: i'mm looking througgh, we resolved to go with option 2. the propsed shape is?<br> <astearns> https://github.com/w3c/csswg-drafts/issues/7589#issuecomment-1380842759<br> <argyle> flackr: its all consistentent with the earlier resolution, but it's not going to end delay and start delay because we moved it to it's own property<br> <argyle> astearns: its in this comment here?<br> <argyle> astearns: yep, this is it<br> <argyle> astearns: alright, any opinions, concerns?<br> <argyle> kevin ellis: moving from timing otpoins to animation options, would no logner be able to update range start/end updating timing<br> <argyle> kevin ellis: we will need web animation api calls on the a nimation object to be able to get range start/end<br> <argyle> kevin ellis: do we have a proposal for getter/setter or function for setting animation range programatically?<br> <argyle> flackr: conventionally we'd do the same thing as animation timeline. getter/setter<br> <argyle> kevin ellis: i'm in support of that, would like to see resolution<br> <argyle> flackr: happy to make that part of the resolution<br> <argyle> astearns: any other comments?<br> <argyle> astearns: any concern with resolving ono this today?<br> <argyle> astearns: proposed is to take the api shape in the linekd comment and add properties to the animation interface along timeline<br> <bramus> SGTM<br> <argyle> astearns: any objections to the propsoed resolution?<br> <argyle> astearns: hearing none, we are resolved<br> <argyle> RESOLVE: take the api shape int he linked comments and add properties to the animation interface along timeline<br> <argyle> RESOLVEd: take the api shape int he linked comments and add properties to the animation interface along timeline<br> <argyle> RESOLVED: take the api shape int he linked comments and add properties to the animation interface along timeline<br> <argyle> astearns: anything more on this one?<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7589#issuecomment-1412415513 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 February 2023 17:11:01 UTC