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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu May 13 17:12:03 PDT 2021


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

--- Comment #3 from Ryosuke Niwa <rniwa at webkit.org> ---
(In reply to Ryosuke Niwa from comment #1)
> Maybe the issue here is that CSSFontFace::m_status is initialized to
> Status::Loaded?

I think this is still the issue. In particular, we rely on style resolution to find fonts in use. So if there was no style resolution by the time Document::implicitClose() is called, then we may fail to detect any fonts available in the document.

The reason this is flaky in Safari is probably because Safari injects scripts to run the reader availability and other things so it's probably triggering a style resolution before load event is fired in some cases.

-- 
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/20210514/e8425958/attachment-0001.htm>


More information about the webkit-unassigned mailing list