Firefox Nightly does not respect system font choice in PBM
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox113 | --- | unaffected |
| firefox114 | --- | wontfix |
| firefox115 | --- | fixed |
People
(Reporter: asdfghrbljzmkd, Unassigned)
References
(Regression)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/114.0
Steps to reproduce:
Have a custom font set as the system font in Gnome Tweaks (e.g. Comic Sans MS)
Actual results:
Firefox does not use the system font in Firefox's interface
Expected results:
Firefox used to use the selected system font in Firefox's interface
Note: I tried selecting the font manually in Firefox's settings, but that didn't work either.
Comment 1•2 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 correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
Do you have private browsing mode enabled or so? Does this reproduce on a clean profile? Is there any chance you could bisect to see when this broke on your setup? Something like:
$ pip3 install --user mozregression
$ mozregression --good 108
(Assuming 108 used to work)
Comment 3•2 years ago
|
||
(In reply to QwertyChouskie from comment #0)
Note: I tried selecting the font manually in Firefox's settings, but that didn't work either.
Do you mean that it appeared in the font list in Firefox settings, but failed to work when you chose it? Or was it missing from the list altogether?
| Reporter | ||
Comment 4•2 years ago
|
||
I just testing disabling Private Browsing mode and it loaded the font as expected, so it appears that a recent change to Private Browsing mode broke things.
Comment 5•2 years ago
|
||
Yeah that would be bug 1826408...
| Reporter | ||
Comment 6•2 years ago
|
||
Setting layout.css.font-visibility.private to 3 worked around the issue.
Comment 7•2 years ago
|
||
:timhuang, since you are the author of the regressor, bug 1826408, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 8•2 years ago
|
||
I think this is really a symptom of bug 1829160, and that's what we should address to fix it.
Comment 9•2 years ago
|
||
As comment 8 suggested, Bug 1829160 should fix this issue. We can verify this after Bug1829160 lands.
Note that this issue should be Nightly only because we only enable this in the Nightly channel.
Comment 10•2 years ago
|
||
As Bug 1829160 landed, could you verify this issue with the latest Nightly to see if the problem gets solved? Thanks.
Comment 11•2 years ago
|
||
Set release status flags based on info from the regressing bug 1826408
| Reporter | ||
Comment 12•2 years ago
|
||
Works, thanks for the quick fix :)
(It won't let me close as duplicate for some reason)
Updated•2 years ago
|
Updated•2 years ago
|
Description
•