- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Feb 2023 10:18:27 +0000
- To: public-css-archive@w3.org
jakearchibald has just created a new issue for https://github.com/w3c/csswg-drafts:
== [css-view-transitions-1] Avoid duplicate unhandled rejections ==
In the current spec, this will cause three unhandled rejections:
```js
const transition = document.startViewTransition(() => {
doesNotExist();
});
```
As it will cause `transition.updateCallbackDone`, `transition.ready`, and `transition.finished` to reject with the same error.
This doesn't seem great, as there's only really one error.
Instead, `transition.ready` and `transition.finished` should not trigger unhandled rejections if they're rejecting for the same reason as `transition.updateCallbackDone`.
@fantasai @tabatkins @astearns I think this is small and uncontroversial enough to be an async resolution.
PR: https://github.com/w3c/csswg-drafts/pull/8454
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8455 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 February 2023 10:18:29 UTC