On Mac, many users use 3rd party font managers which can store fonts on the filesystem anywhere the user chooses. We should have a test that installs a font from a non-standard directory and then renders a page using that font, making sure the font is displayed correctly.
Assignee: nobody → haftandilian
Priority: -- → P2
Created attachment 8944816 [details] Source for CLI command to register/unregister fonts A CLI command that registers or unregisters fonts in place. Using this command, we could register a font from a non-standard location, display a page that depends on this font, validate the page is displayed correctly, then uninstall the font. Any directory not included in our content sandbox read-access whitelist is considered a non-standard font directory. For example, ~/MyFonts/font.otf.
Created attachment 8944874 [details] Python CLI command to register/unregister fonts Register/unregister fonts in python to make this easier to use in automated tests--no compilation required.
You need to log in before you can comment on or make changes to this bug.