304381 2025-12-17 21:07:20 -0800 A FontFaceSet created with `new FontFaceSet` doesn't get unblocked by document loading 2026-01-05 15:05:24 -0800 1 1 1 Unclassified WebKit DOM WebKit Nightly Build Unspecified Unspecified RESOLVED WONTFIX https://bugs.webkit.org/show_bug.cgi?id=276794 InRadar P2 Normal --- 1 simon.fraser webkit-unassigned simon.fraser webkit-bug-importer oldest_to_newest 2166828 0 simon.fraser 2025-12-17 21:07:20 -0800 FontFaceSet has a notion of "pending on the environment"[1], which generally means waiting for document load. This blocks resolving the ready promise. FontFaceSets created in script (like `new FontFaceSet`) are never registered to be notified when document load completes; we only notify the fontSelector's FontFaceSet: if (RefPtr fontSelector = fontSelectorIfExists()) { if (RefPtr fontFaceSet = fontSelector->fontFaceSetIfExists()) fontFaceSet->documentDidFinishLoading(); I had to fix LayoutTests/fast/text/font-loading-multiple-sets.html to work around this. [1] https://drafts.csswg.org/css-font-loading/#fontfaceset-pending-on-the-environment 2167096 1 simon.fraser 2025-12-18 15:15:56 -0800 Moot after bug 276794 is fixed. 2168114 2 webkit-bug-importer 2025-12-24 21:08:10 -0800 <rdar://problem/167157912> 2169486 3 simon.fraser 2026-01-05 15:05:24 -0800 The FontFaceSet constructor was removed.