FWIW, the comment came from the equivalent function for the old Gecko styling system; https://searchfox.org/mozilla-central/diff/b4e5e8f7289cea684a11c99340bc25e5e66f70a1/dom/canvas/CanvasRenderingContext2D.cpp#2801-2803 Anyway, honestly I don't recall how we set up the font resolving function. My (best) wild guess was resolving the given font declaration with using the parent style should fix this bug. But we do already [do it](https://searchfox.org/mozilla-central/rev/0ffae75b690219858e5a45a39f8759a8aee7b9a2/dom/canvas/CanvasRenderingContext2D.cpp#2480). And surprisingly when I load the test case in comment 0 from my local disk, the problem doesn't happen. If this bug is urgent, I will jump. (Presumably just flushing pending styles before getting the parent style would solve?)
Bug 1766356 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
FWIW, the comment came from the equivalent function for the old Gecko styling system; https://searchfox.org/mozilla-central/diff/b4e5e8f7289cea684a11c99340bc25e5e66f70a1/dom/canvas/CanvasRenderingContext2D.cpp#2801-2803 Anyway, honestly I don't recall how we set up the font resolving function. My (best) wild guess was resolving the given font declaration with using the parent style should fix this bug. But we do already [do it](https://searchfox.org/mozilla-central/rev/0ffae75b690219858e5a45a39f8759a8aee7b9a2/dom/canvas/CanvasRenderingContext2D.cpp#2480). And surprisingly when I load the test case in comment 0 from my local disk, the problem doesn't happen. If this bug is urgent, I will jump in. (Presumably just flushing pending styles before getting the parent style would solve?)