[Webkit-unassigned] [Bug 225790] document.fonts.ready is sometimes still resolved too quickly

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Jul 24 09:28:04 PDT 2022


https://bugs.webkit.org/show_bug.cgi?id=225790

Ahmad Saleem <zlip.792 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zlip.792 at gmail.com

--- Comment #13 from Ahmad Saleem <zlip.792 at gmail.com> ---
Based on the test case from Comment 0, I am getting following results across all browsers:

NOTE - All testing performed within Private / Incognito Mode with Multiple refresh to trigger unloaded issue.

*** Safari 15.6 on macOS 12.5 ****

FontFaceSet.status in onload:   loaded
FontFace.status in onload:      loaded
FontFaceSet.status after ready: loaded
FontFace.status after ready:    loaded

*** Chrome Canary 106 ****

FontFaceSet.status in onload:   loading
FontFace.status in onload:      loaded
FontFaceSet.status after ready: loaded
FontFace.status after ready:    loaded

*** Firefox Nightly 104 ****

FontFaceSet.status in onload:   loading
FontFace.status in onload:      loaded
FontFaceSet.status after ready: loaded
FontFace.status after ready:    loaded

Just wanted to share updated results. I am not sure whether something change in web-spec or when Firefox decided to follow Chrome for FontFaceSet but this is as of today updated results. Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220724/3bbb5ed4/attachment-0001.htm>


More information about the webkit-unassigned mailing list