This affects beta 87.0 (64-bit) and dev edition 87.0b9 (64-bit) as well. and the issue is a bit different than nightly there (it's worse), that the "PingFang SC Regular" (wrong font) is used regardless of how long I wait before opening the page. Looks like it's because bug 1533462 change isn't enabled for beta/dev edition. I see that `gfx.e10s.font-list.shared` pref is `false` there, and flipping it to `true` changes the behavior that the wrong font is used only when I open the page immediately after starting Firefox (so, same as nightly) Then, the issue about "wrong font is used for monospace" affects release 86.0.1 (64-bit). as described in comment #8 above, it's always "Hiragino Kaku Gothic ProN W3" there. (so I guess the issue has been there from 76) :jfkthame, does the patch also fix `gfx.e10s.font-list.shared == false` case?
Bug 1697666 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This affects beta 87.0 (64-bit) and dev edition 87.0b9 (64-bit) as well. and the issue is a bit different than nightly there (it's worse), that the "PingFang SC Regular" (wrong font) is used regardless of how long I wait before opening the page. Looks like it's because bug 1533462 change isn't enabled for beta/dev edition. I see that `gfx.e10s.font-list.shared` pref is `false` there, and flipping it to `true` changes the behavior that the wrong font is used only when I open the page immediately after starting Firefox (so, same as nightly) Then, the issue about "wrong font is used for monospace" affects release 86.0.1 (64-bit). as described in comment #8 above, it's always "Hiragino Kaku Gothic ProN W3" there. (so I guess the issue has been there from 76) :jfkthame, does the patch also fix `gfx.e10s.font-list.shared == false` case? (I'll test locally, but want to make sure)