- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Mar 2023 15:31:04 +0000
- To: public-css-archive@w3.org
jakearchibald has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-view-transitions-2] Get data on type of 'finished' state == Right now, [`transition.finished`](https://drafts.csswg.org/css-view-transitions-1/#dom-viewtransition-finished) resolves when the final DOM state is reached, visually. This includes cases where the transition has skipped, or even failed to start. This was what folks seemed to expect in practice (and aligns with [`animation.finished`](https://drafts.csswg.org/web-animations-1/#dom-animation-finished)), but there are also cases where you want to know if the transition was skipped, and why. Use-cases include testing, and monitoring. To provide this, `transition.finished` could fulfill with a value: ```js const result = await transition.finished; ``` Where result indicates the various types of 'finished': - Played through to completion. - Skipped by developer, via `transition.skipTransition()`. - Skipped because of newer transition. - Skipped because of invalid state. We could go into more detail about 'invalid state', eg was it a window resize, or a constraint broken on a particular transition element. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8624 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 March 2023 15:31:05 UTC