On Tor Browser 11.0.4 on macOS 10.15.7, any element with font-family: monospace doesn't render correctly: it uses Times or Helvetica instead, depending on context. This doesn't seem to happen on Linux. I haven't had time to bisect to determine when this bug started happening. It also showed up on a recent alpha; not sure which version exactly.
An easy way to see this is to create a .txt file with some text and open it using a file:/// URL. Observe that it is not displayed with a monospaced font. Open the Inspector, and observe that under "Fonts Used", the font is not a monospaced font. This affects even the rendering of monospaced HTML and CSS code displayed within the Inspector itself. Some webpages with monospaced text happen to display correctly due to explicitly named fonts in their CSS addition to the monospace name.
Explicitly adding "Menlo" to font.system.whitelist appears to work around the problem.
Designs
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
e9dbacf3 seems to have introduced the font change to Menlo on macOS. The overrides in 266d8540 happened later, interacting to produce the bug. The default font.system.whitelist doesn't include Menlo, and the macOS setting for font.name-list.monospace.x-unicode does include Courier, which is whitelisted, but it looks like the default language ends up being x-western, at least for my installation.
Very few of the other monospace font name lists are updated to include only whitelisted fonts. If there's some reason to not whitelist Menlo, then many other settings may need to be changed.
I think so, but IANAE. I was thinking about it earlier. Probably not for entropy, but it looks like we only change a few (most of the bundled fonts match optional mac downloads so probably already match), but in reality we should ensure each one matches what is in the whitelist, and consistently, e.g. not have Courier for some and Menlo for others. At least that way we minimize broken script support
TBH, we should ask someone like jfkthame, but he's very hard to get hold of. Easy to talk to in bugzilla, but I reckon it needs someone with some gravitas like tor project users or maybe tom to reach out and ask a mozilla font person, maybe henri?
Side Note: We should add Consolas to Windows whitelist sooner rather than later (it's actually a nicer font TBH)
FF99 changed a default font - consolas instead of courier new
I think so, but IANAE. I was thinking about it earlier. Probably not for entropy, but it looks like we only change a few (most of the bundled fonts match optional mac downloads so probably already match), but in reality we should ensure each one matches what is in the whitelist, and consistently, e.g. not have Courier for some and Menlo for others. At least that way we minimize broken script support
I see, thank you anyway!
Side Note: We should add Consolas to Windows whitelist sooner rather than later (it's actually a nicer font TBH)
FF99 changed a default font - consolas instead of courier new
Anyway, the name-list preferences seem to be used in browser/components/preferences/dialogs/fonts.js.
They seem to be linked to Advanced font settings (hence also the language), but they don't have an associated element.