W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2019

[csswg-drafts] FontFaceSet.ready resolve-time (#4248)

From: Sam Sneddon via GitHub <sysbot+gh@w3.org>
Date: Wed, 28 Aug 2019 14:23:38 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-486415719-1567002216-sysbot+gh@w3.org>
gsnedders has just created a new issue for https://github.com/w3c/csswg-drafts:

== FontFaceSet.ready resolve-time ==
https://drafts.csswg.org/css-font-loading/#font-face-set-ready

This appears to be pretty vague as to when it resolves:

> The ready attribute contains a Promise which is resolved when the document is done loading fonts, which provides a way for authors to avoid having to keep track of which fonts have or haven’t been loaded before examining content which may be affected by loading fonts.

At what point is the document "done loading fonts"? It would be good to add some cross-reference to something for this. Which document? Or is this meant to be informative and the normative definition that in "switch the FontFaceSet to loaded"?

Per https://github.com/web-platform-tests/wpt/pull/17219#issuecomment-521909714, it seems Blink and Gecko wait until after the first layout, whereas WebKit resolves once it has loaded but before layout is done (should add tests for fallback!). The IDL block has a comment `// async notification that font loading and layout operations are done` but the "layout operations" part doesn't seem to be backed up by any normative text?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4248 using your GitHub account
Received on Wednesday, 28 August 2019 14:23:39 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:52 UTC