W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2020

Re: [csswg-drafts] [web-animations-1] Finished pending state (#5452)

From: verbessern via GitHub <sysbot+gh@w3.org>
Date: Thu, 20 Aug 2020 04:20:15 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-677016057-1597897214-sysbot+gh@w3.org>
I wish I could. I'm talking about the finished notification micro task (FN), that must be a micro task according to the specs: "Otherwise, if synchronously notify is false, **queue a microtask** to run finish notification steps for animation unless there is already a microtask queued to run those steps for animation." The test would have the following steps:
```
All animations are updated
  asynchronously FN is queued as FNmt
MicroTask are run
  FNmt is run
    the finished promise is resolved
      FPmt is queued as a micro task also
  FPmt is run
    it changes the animation to become again asynchronously queued as FNmt
  .. loop
```
The tasks that are not run as micro tasks do not have this issue, as for example the ready one. If its queued as a micro task however it would have it also. The thing is that, it must be guarantied that the resolved promises inside micro tasks, do not change animations, but i think that is the whole idea. If the current implementations that use the animation engine (CSS, SVG, I don't know) can't craft such a case, good, else...bad.

-- 
GitHub Notification of comment by verbessern
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5452#issuecomment-677016057 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 August 2020 04:20:17 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:13 UTC