Bug 305470 – Safari 26.2 broke `document.fonts.loadingdone`

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: Text

Created attachment 478016 [details]
Safari 26.2 vs Google Chrome

Safari 26.2 partially broke the CSS Font Loading API, namely, the loadingdone event. (https://developer.mozilla.org/en-US/docs/Web/API/FontFaceSet/loadingdone_event)

```ts
document.fonts.addEventListener('loadingdone', function() {
  console.log('Does not register on Safari 26.2');
});
```

- In the following fiddle JSFiddle, you can see that `loadingdone` is never fired: https://jsfiddle.net/7yzsv6ek/

[Alexey Proskuryakov]

Thank you for the report! Checking related issues, I don't think that 26.2 broke "loadingdone" - what happened was that the "loading" event got implemented without also implementing "loadingdone". Testing with Safari 26.1, I see an empty event log.

loadingdone was very recently implemented, duping to that issue.

*** This bug has been marked as a duplicate of bug 304091 ***

(In reply to Alexey Proskuryakov from comment #1)
> Thank you for the report! Checking related issues, I don't think that 26.2
> broke "loadingdone" - what happened was that the "loading" event got
> implemented without also implementing "loadingdone". Testing with Safari
> 26.1, I see an empty event log.
> 
> loadingdone was very recently implemented, duping to that issue.
> 
> *** This bug has been marked as a duplicate of bug 304091 ***

Thanks! That makes sense.