- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Nov 2024 06:06:22 +0000
- To: public-css-archive@w3.org
> I started reviewing this today, just briefly, but I'm still trying to get my head around how this will work with #5394 (and whether we can truly do without #11085). So to capture my working, in #5394 we're proposing that calling `commitStyles` on an animation that doesn't fill and has just finished captures the final value (i.e. ignores the endpoint exclusive timing). Suppose we have an animation from width 100px to 200px, no fill mode, and we call `commitStyles` as part of its finished event. Let's assume the unanimated width (i.e. base style width) is 50px (just to make it easier to distinguish the animation style from the base style). 1. `commitStyles` is called. 2. We flush styles to ensure everything is up-to-date. 3. At this point the inline style has yet to be updated so there is no change to the base value (it's still 50px) and no transition is triggered. 4. We calculate the final value of the animation as 200px and update the inline style to 200px. 5. On the next style change event, we notice that the base width has gone from 50px to 200px. Furthermore, during the previous style change event (2~3) `width` was not "affected by an animation" and hence we trigger a transition—which I don't think we intend to. Does that seem right? -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/6688#issuecomment-2475490626 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 14 November 2024 06:06:23 UTC