- From: verbessern via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Aug 2020 05:51:50 +0000
- To: public-css-archive@w3.org
If I can speculate, I think that the whole idea of the asynchronous tasks is to do the 'job' outside of the animations update procedure. If that is the only reason to use the microtask queue, I would vote for a specific queue, that holds the tasks that were queued during the animations update, and just after the update, to run this tasks. Because this tasks by themselfs cant queue any more tasks, this queue will run linearly. Maybe before or after step 2 in "update animations and send events". Then when the microtasks queue is not at all used, the promises may do any kind of job, and will never stall the engine. -- GitHub Notification of comment by verbessern Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5452#issuecomment-677203891 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 05:51:52 UTC