- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Oct 2022 20:20:59 +0000
- To: public-css-archive@w3.org
vmpstr has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-view-transitions-1] Should the DOMChangeCallback be posted as a task from skip transition steps? == Step 4 in [skip the page transition algorithm](https://drafts.csswg.org/css-view-transitions-1/#skip-the-page-transition-algorithm) says that the DOM change callback has to be invoked synchronously. However, the skip the page transition algorithm sometimes runs as part of the update the rendering, and we really want to avoid running (new) script in those steps. We should make it asynchronous. The question is should we just make it asynchronous for all places that run the skip the page transition algorithm, or should it be conditional? I'm leaning towards just make it all asynchronous, but I'm unsure if there are cases where synchronous invocation is important. /cc @khushalsagar @jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7904 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 October 2022 20:21:01 UTC