Additional data point: the font renders correctly if you try to use it a second time after a long timeout.

We expect that after loading is complete, the font would be immediately available for rendering, and that any outstanding preparation tasks would be performed synchronously at that time.

What seems to be happening is that there is a and additional async preparation step that still needs to be performed after the the load promise is resolved.  The first attempt to use the font for drawing to a canvas lazily triggers this, and at a later time, the font resource becomes good to go.


 

There is a common pitfall of CSS Font Loading API -- FontFace must be added to document.fonts before using.

fserb@, can you try attached fontface2.html? This works for me.

Deleted: fontface2.html 627 bytes

fontface2.html 627 bytes View Download

Since ksakamoto@ already replied, I'd assign this to ksakamoto@.

this seems to work. Thanks.