- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Aug 2022 15:03:37 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `breakout summary`, and agreed to the following: * `RESOLVED: Adopt the previously-skipped bullet point from fantasai's summary` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: breakout summary<br> <TabAtkins> github: https://github.com/w3c/csswg-drafts/issues/7044<br> <TabAtkins> flackr: we established the keyframe offsets never change the animation timing, they're offsets as normal<br> <TabAtkins> flackr: same mechanism could also address the request from users to be able to set keyframes to particular times, like "500ms after the start of the animation"<br> <TabAtkins> flackr: i think we were all ok with this line of thinking<br> <TabAtkins> I'm okay with this<br> <TabAtkins> ydaniv: 100% correct<br> <TabAtkins> ydaniv: if this allow smore flexibility and sugaring, taht's great<br> <TabAtkins> ydaniv: if other libraries want to create reusable effects that's also possible<br> <TabAtkins> astearns: so proposed resolution is to adopt the skipped bullet point<br> <TabAtkins> RESOLVED: Adopt the previously-skipped bullet point from fantasai's summary<br> <TabAtkins> bramus: In a follow up comment, i said it should be easy for authros to reuse exisitng keyframes for a phase<br> <TabAtkins> bramus: like a generic animation library with a fade-in or fade-out, should be able to say "use this keyframes fro the entry phase"<br> <TabAtkins> ydaniv: sounds good for animation 2<br> <TabAtkins> fantasai: do we already have this?<br> <TabAtkins> flackr: yes, but for separate keyframe rules<br> <TabAtkins> bramus: so i'd like to be able to say...<br> <bramus> https://www.irccloud.com/pastebin/vPjQFIza/<br> <bramus> @keyframes bla {<br> <bramus> enter fade-in;<br> <bramus> exit fade-out;<br> <bramus> }<br> <TabAtkins> bramus: and maybe the ability to say `enter 50% fade-in`, etc<br> <TabAtkins> fantasai: so the ability to say start, end, and the name of a @keyframes<br> <TabAtkins> fantasai: similar to syntax we ahve for the animation-phase shorthands<br> <TabAtkins> fantasai: i think that makes a lot of sense, but also is def a separate issue<br> <flackr> +1<br> <TabAtkins> fantasai: happy to resolve if we want to do this, but should probably open a separate issue to flesh it out<br> <TabAtkins> astearns: i heard an opinion that this should be next level<br> <TabAtkins> fantasai: yeah and this def isn't a scroll-animations issue, it's a general animations issue<br> <TabAtkins> miriam: this is basically being able to compose scenes out of an animation<br> <TabAtkins> ydaniv: in animation-2 we have group/sequence, doesn't this map to that?<br> <TabAtkins> flackr: those can overlap so compositing is a complex topic<br> <TabAtkins> TabAtkins: but yeah this is related<br> <TabAtkins> fantasai: so yeah great idea, should be generic to all animations<br> <TabAtkins> astearns: given this is a new idea, i'd like to see a new issue with the proposed syntax, give people a chance to look at it before resoling<br> <TabAtkins> bramus: i'll open a new issue<br> <TabAtkins> astearns: in the animations-2 tag<br> <flackr> css-animations-2 i think this would be?<br> <TabAtkins> yes<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7044#issuecomment-1204069377 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 August 2022 15:03:39 UTC