In #13313 (moved) we whitelisted fonts by file name. But as dcf points out, it would be ideal to whitelist bundled fonts only, using the font file path. As far as I can tell this will need to be implemented separately for Windows, Mac, and Linux.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
So I tried a simple and dumb thing to disable system fonts with Fontconfig, and it mostly works! All I did was comment out FcSetSystem leaving only FcSetApplication. I tested this patch on top of tbb-5.0a4-build2; i.e., with the Noto fonts installed but without the font whitelisting patch of #13313 (moved).
It seems like the only negative side effect of the patch is an extension of the monospace font thing in comment:6:ticket:16672. Not only is it monospace in the tab titles and URL bar, but also Latin text in web pages is rendered using the monospace Cousine font. This might just be because the branch I built did not have the font prefs that came along with the whitelisting patch.
(BTW we [[comment:1:ticket:13313|already know]] that you can whitelist a directory in Fontconfig using fonts.conf; this is another way.)