If font.system.whitelist does not include any available fonts, disable whitelisting (as if the list were empty)
Categories
(Core :: Graphics: Text, enhancement, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox70 | --- | fixed |
People
(Reporter: jfkthame, Assigned: jfkthame)
Details
Attachments
(1 file)
If the font.system.whitelist pref (from bug 1121643) is empty, no whitelist is applied and all installed fonts are available to the browser.
If it lists one or more of the system's installed font families, only these are available to use.
However, if the pref is non-empty, but does not list any font families that are actually installed, what should happen? Currently, when the list of installed fonts is being filtered by the whitelist, we just ensure that the last entry is not deleted, so one font will remain available. Which font this will be is rather arbitrary, depending on the order of iteration over the font-families hashtable.
I don't think this is particularly good behavior: it's arbitrary and unpredictable, and it can result in the only available font being something like a symbol or dingbat font that is not really useful at all - at which point the Firefox UI becomes pretty unusable, with things like about:config becoming unreadable.
A more sensible option, I think, would be to treat a whitelist containing no available fonts the same as an empty whitelist, and just not filter the list at all. This avoids the arbitrariness of just picking the "last font standing", and potentially leaving the user with a broken UI.
| Assignee | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Comment 2•6 years ago
|
||
Bugbug thinks this bug is a enhancement, but please change it back in case of error.
Comment 4•6 years ago
|
||
| bugherder | ||
Updated•6 years ago
|
Description
•