- From: Mark via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Oct 2024 11:59:19 +0000
- To: public-css-archive@w3.org
> If this is achieved, the promise should be fulfilled; if not, the promise should be rejected. This is a valid point @webdevelopers-eu. But I think throwing an error may be unexpected for these cases and developers are probably likely to miss handling it. Is it possible to just abort/cancel the promise instead? That would make it so that an app handles this gracefully (by default) instead of abruptly throwing an error, which could potentially cause an entire website from working if it's a SPA (or javascript-heavy). -- GitHub Notification of comment by markcellus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1562#issuecomment-2413716665 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 15 October 2024 11:59:20 UTC