Issue with incorrect Japanese font on 135
Hello,
I have encountered an issue on some websites where the Japanese text is using the font "Microsoft YaHei" when it should be using "Meiryo." Some examples are on the website bluesky, and bold text on Twitter such as in usernames.
I originally thought it was an issue on my end or in Windows, but when checking other programs and websites such as dengekionline and the non-bold text on Twitter it is using the correct font which I have confirmed via the inspector under the font section. When starting Firefox in safe mode it seems to use the correct font on the previously mentioned websites, so I disabled all my extensions and themes and this did not resolve the issue. I did a Firefox Refresh and this also did not resolve the issue.
I am not familiar with the intricacies on the Firefox about:config to really delve into the exact cause, so I ended up just reverting back to Firefox 134. On Firefox 134 with my same extensions previously the font is now back to Meiryo as it should be which leads me to believe it is something that was changed in Firefox 135. One thing I am considering is that the Japanese text is being recognized as Simplified Chinese by Firefox 135 as Simplified Chinese uses the Microsoft YaHei font as a default.
I have attached some photos that shows my Japanese font settings, and the same post by a user one on Firefox 135 which is using Microsoft YaHei and another on Firefox 134 which is using the correct Meiryo. I have also tried disabling the "Allow pages to choose their own fonts, instead of your selections above" and then restarting on 135, but this did not resolve the issue. Thank you for your consideration.
All Replies (1)
Just to add some more information. I updated to Firefox 135 once again and then changed the "Simplified Chinese" font settings to match what the Japanese settings are and the font is showing correctly, so I believe my suspicion was correct in assuming that the Japanese characters are being recognized as Simplified Chinese by Firefox. Would like to know if this is just a bug or if this can be resolved, thank you.