PMingLiU is incorrectly specified as the default sans-serif font for zh-TW
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox137 | --- | fixed |
People
(Reporter: pan93412, Assigned: jfkthame, NeedInfo)
References
Details
Attachments
(5 files)
Steps to reproduce:
Open the following page in Firefox on Windows:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Document</title>
<style>
body {
font-family: sans-serif;
}
</style>
</head>
<body>
測試中文 ABCD
</body>
</html>
Actual results:
You will see Firefox select "PMingLiU" (which is a Serif font) for "sans-serif".
Expected results:
For any other browsers (Edge 133.0.3065.39 and Chrome 133.0.6943.54), the real sans-serif font "Microsoft JhengHei" is selected.
Reporter | ||
Comment 1•7 months ago
|
||
Reporter | ||
Updated•7 months ago
|
Reporter | ||
Comment 2•7 months ago
|
||
Note that Firefox selects the correct sans-serif font on Firefox Beta [1], and it should be
Reporter | ||
Comment 3•7 months ago
|
||
(In reply to Yi-Jyun Pan from comment #2)
Note that Firefox selects the correct sans-serif font on Firefox Beta 1, and it should be
Sorry for the incomplete comment; I submitted it accidentally.
Firefox selects the correct sans-serif font, Microsoft JhengHei, on Firefox Beta 1. It previously selected this font in the stable version until Issue 1517937 arose. Since Chromium has updated its sans-serif font to Microsoft JhengHei 2, I believe it is no longer necessary to choose PMingLiU for sans-serif.
Reporter | ||
Comment 4•7 months ago
|
||
Reporter | ||
Updated•7 months ago
|
Comment 5•7 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Layout: Text and Fonts' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 6•7 months ago
|
||
ref, the behavior is defined at https://hg.mozilla.org/mozilla-central/file/tip/modules/libpref/init/all.js#l2142
Comment 8•7 months ago
|
||
zh-TW locale owner here, some background information:
- In Bug 1394709 we added Microsoft JhengHei to the font fallback list.
- In Bug 1517937c3, some user complained about having MSJH before PMingLiu as a default, so we moved MSJH to the end of preference list for Release, and keep it first (as zh-TW default font) in Beta and Nightly.
- Chrome and Edge also had their default changed to MSJH in 2016 to use modern zh fonts [1].
After all these years, I believe it's time again to make it default for all channels.
Assignee | ||
Comment 9•7 months ago
|
||
(In reply to Peter Pin-Guang Chen [:petercpg] (MozTW.org) from comment #8)
zh-TW locale owner here, some background information:
- In Bug 1394709 we added Microsoft JhengHei to the font fallback list.
- In Bug 1517937c3, some user complained about having MSJH before PMingLiu as a default, so we moved MSJH to the end of preference list for Release, and keep it first (as zh-TW default font) in Beta and Nightly.
- Chrome and Edge also had their default changed to MSJH in 2016 to use modern zh fonts [1].
After all these years, I believe it's time again to make it default for all channels.
I agree this is the right thing to do. (I suspect we may still get some pushback from people who dislike the change, but the current configuration doesn't really make sense.)
Assignee | ||
Comment 10•7 months ago
|
||
We've been shipping this configuration on Nightly/early-Beta since bug 1394709
(7 years ago), but temporarily reverted it for late-Beta/Release in bug 1517937
due to issues with the JhengHei font and some users' preference for the old
PMingLiu face.
But as reported in this bug, PMingLiu really isn't an appropriate mapping for
'sans-serif', and as :petercpg suggests in [1], it seems like time to ship
this change.
Updated•7 months ago
|
Comment 11•7 months ago
|
||
Also, the behavior difference between the release and beta confused people. Users who think this is a bug easily believe that it will be fixed in the next release.
Comment 12•7 months ago
|
||
Comment 13•7 months ago
|
||
bugherder |
Updated•6 months ago
|
Comment 14•6 months ago
|
||
I tried to reproduce the issue on a Firefox Nightly 137.0a1(2025-02-06) on a zh-TW locale on both Windows 10/ Windows 11 with no success.
Given the case, can you please confirm that the issue is fixed on the latest Firefox 137 beta build? Thank you.
Description
•