[css-font-loading] Timing clarification of ready attribute/promise


I am trying to get a clearer picture on the exact timing of the ready
promise getting resolved:

>From https://drafts.csswg.org/css-font-loading/#font-face-set-ready :
"The ready attribute contains a Promise which is resolved when the
document is done loading fonts"

And further down, in the non-normative note:
"The ready promise is only fulfilled after layout operations complete
and no additional font loads are necessary."

What I noticed in Chrome, while working on a larger font-loading
related test case:
Depending on machine performance, there is a small delay <100ms
between the promise getting resolved, and the fonts actually being
used for rendering. And I am curious whether this - in the spirit of
the spec - a bug or acceptable behaviour.

Does the "after layout operations complete" note imply that the fonts
that just completed loading are used for rendering and the screen is
updated with those?

Could the timing of this promise-resolution be made more exact and and
moved from the note to a normative statement?



Received on Wednesday, 5 August 2015 21:40:26 UTC