228909 2021-08-09 00:33:41 -0700 document.fonts.ready stays unresolved 2021-09-13 19:06:14 -0700 1 1 1 Unclassified WebKit Page Loading Safari 14 All All RESOLVED CONFIGURATION CHANGED InRadar P2 Normal --- 1 roland webkit-unassigned achristensen beidson cdumez mmaxfield webkit-bug-importer oldest_to_newest 1782839 0 roland 2021-08-09 00:33:41 -0700 Steps to reproduce: 1. Open https://www.soelvahof.com/kaltern/kaltern/ A lot of time the `document.fonts.ready` stays unresolved. Check its state in the console. 1782844 1 roland 2021-08-09 01:13:06 -0700 It might be related to the fact that window's load event is not happening. `document.readyState` is "complete", but `window.performance.timing.loadEventStart` and `window.performance.timing.loadEventEnd` is 0 1784428 2 webkit-bug-importer 2021-08-16 00:34:21 -0700 <rdar://problem/81969526> 1792271 3 mmaxfield 2021-09-10 01:28:49 -0700 rdar://82962890 is stopping me from investigating this. Hopefully that bug can be fixed soon so I can investigate this document.fonts bug. 1792602 4 mmaxfield 2021-09-10 16:48:53 -0700 I modified this bit of code in n2.min.js fonts: new Promise((function(t) { "fonts" in s ? (s.fonts.ready.then(t), h.r("windowLoad", t)) : h.r("windowLoad", t) })) to be this: fonts: new Promise((function(t) { s.fonts.ready.then(function() {debugger;}); "fonts" in s ? (s.fonts.ready.then(t), h.r("windowLoad", t)) : h.r("windowLoad", t) })) and the "debugger" line did get hit in macOS Monterey. 1792608 5 mmaxfield 2021-09-10 16:54:45 -0700 And, above, when the `debugger;` line gets hit, > document.readyState < "complete" > window.performance.timing.loadEventStart < 1631318004941 > window.performance.timing.loadEventEnd < 1631318004941 1792647 6 mmaxfield 2021-09-10 21:08:49 -0700 <rdar://problem/81969526> 1793182 7 mmaxfield 2021-09-13 19:06:14 -0700 I'm not able to reproduce this, given the above analysis, so I'm going to mark this as "configuration changed." If this is still happening, please re-open the bug.