Serif font preference resetting to Times New Roman
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
People
(Reporter: ffzilla, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.61 Safari/537.36 Edg/94.0.992.31
Steps to reproduce:
Hello. I wanted to use Liberation Serif font as my Serif on MS Windows 10 with Firefox 92.0.1 (and Liberation Mono as the default Monospace font).
System wide installed Liberation fonts were not listed in the Firefox font drop-down menus, and I realized it is because of privacy.resistFingerprinting being set to true.
Then I manually installed the TTF version of Liberation fonts in the directory C:\Program Files\Mozilla Firefox\fonts\ so that they would be available in the Firefox font selection.
Actual results:
Something peculiar happens when I change "Latin" fonts to use Liberation Serif as the serif font and Liberation Mono as the monospace font. After clicking on OK, and opening the Advanced font dialog again the serif font has been reset to "(Default) Times New Roman" every time but the monospace font remains as the preferred "Liberation Mono".
If I delete fonts from C:\Program Files\Mozilla Firefox\fonts\ and I set privacy.resistFingerprinting to false, then my choice of serif sticks. It does not reset to default Times New Roman like it does when fonts are installed in Firefox' own fonts directory and when privacy.resistFingerprinting is set to true.
Some extra details on my specific combination of settings:
Default font: Verdana
Latin proportional: sans-serif
Latin Sans-serif: Verdana (does not reset to default)
Latin Monospace: Liberation Mono (does not reset to default)
Latin Serif: Liberation Serif (resets to default Times New Roman)
Expected results:
Custom preference of the serif font should not have reset to Times New Roman.
|
||
Comment 1•4 years 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 revert this change in case you think the bot is wrong.
|
|
||
Comment 2•4 years ago
|
||
The severity field is not set for this bug.
:mats, could you have a look please?
For more information, please visit auto_nag documentation.
|
|
||
Comment 3•3 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:jfkthame, since the bug doesn't have a severity set, could you please set the severity or close the bug?
For more information, please visit auto_nag documentation.
Description
•