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: Wed, 19 Aug 2020 16:15:09 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-676522551-1597853707-sysbot+gh@w3.org>
OK, my suspicious is growing. When the `pending finished notification micro task` is run, as an element of the `micro task queue`, where the `promises` are also queued (as far as I'm reading around), that means that the `resolving the finished promise` (`finish notification steps, step 2`), may trigger a sequence of changes (play/set current time) to the animation (that its later run in the same micro task cycle), that cause the finish notification micro task, again, asynchronously, to be added to the `micro task queue`. 
This may cause a stall of the micro task queue, because its run till depletion. That effect can't be observed in the play/pause `simple tasks`, because they are not using the micro task queue (at least in the implementation in question), even that they are also resolving a promise (the `ready` one). If what I'm deducting is true, then if the finished notification is also run out of the `micro task queue` as the play/pause tasks, then that could be prevented.

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 August 2020 16:15:11 UTC

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