- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Sep 2022 19:55:55 +0000
- To: public-css-archive@w3.org
The "fulfill the promise if there are no fonts" is just how Promise.all() normally works when fed an empty list (and in particular is how WebIDL works by default, if you refer to its algorithms; this spec was written before those were established, but I should fix to refer to them). Is there a good reason we should diverge from that, or is this just an artifact of browsers doing stuff in idiosyncratic ways before we got good spec algos to encourage consistency? Note that this is also consistent with the current spec for .check(), which returns true if no fonts need to be loaded at all. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7680#issuecomment-1242402857 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 September 2022 19:55:57 UTC