- From: Bramus via GitHub <noreply@w3.org>
- Date: Thu, 26 Mar 2026 15:13:57 +0000
- To: public-css-archive@w3.org
> This rejection comes from skipping the transition on the old document, but this is expected behavior. Should the developer be required to explicitly catch this to avoid the exception? I don’t think the author should handle this, so we should find a way to prevent this from throwing. > An alternative here, is the fulfill the ready promise ahead of the pageswap event so that the pending ready promise is not rejected on document tear down. This could be a solution to bypass the internals, but it would break the contract to the user because `ready` getting fulfilled indicates that the pseudo-tree is ready … unless we alter the meaning of `ready` so that it more broadly indicates that all the capturing work _(old snapshots + new snapshots + pseudo-tree constructed for same-doc; old snapshots for outbound cross-doc)_ has been done. Another solution could be to alter the steps in “skip the view transition” to make “7. Reject transition’s `ready` promise with reason.” conditional: If the transition not the outbound transition of a cross-doc navigation, only then reject the `ready` promise. Looping in @noamr for his take on this. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13726#issuecomment-4135860231 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 March 2026 15:13:58 UTC