- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Feb 2023 09:45:19 +0000
- To: public-css-archive@w3.org
@domenic we kinda discussed this already, but I want to double check with some specifics of this API.
```js
const transition = document.startViewTransition(async () => {
// Update DOM somehow
});
```
- `transition.updateCallbackDone` - rejects/resolves along with the "Update DOM somehow" callback
- `transition.ready` - fulfills when the transition is ready to play. Rejects if `updateCallbackDone` rejects, but may also rejects if the transition cannot start for other reasons.
- `transition.finished` - fulfills when the end state is reached, which is after the transition animation if one happens. Rejects if `updateCallbackDone` rejects, since the end state cannot be reached.
The proposal is to mark `ready` and `finished` as handled if they're being rejected with the same error as `transition.updateCallbackDone`.
Does that sound reasonable?
--
GitHub Notification of comment by jakearchibald
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8455#issuecomment-1436645560 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 February 2023 09:45:21 UTC