[Mac] Add a test that renders fonts from non-standard directories

NEW
Assigned to

Status

()

Core
Security: Process Sandboxing
P1
enhancement
a month ago
29 days ago

People

(Reporter: haik, Assigned: haik)

Tracking

58 Branch
Unspecified
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: sb+)

Attachments

(1 attachment, 2 obsolete attachments)

(Assignee)

Description

a month ago
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)

Updated

a month ago
Assignee: nobody → haftandilian
Priority: -- → P2
(Assignee)

Comment 1

a month ago
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.
(Assignee)

Comment 2

a month ago
Created attachment 8944817 [details]
Script to build the registerfont, unregisterfont commands
(Assignee)

Updated

a month ago
See Also: → bug 1393259
(Assignee)

Comment 3

a month ago
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.
Attachment #8944816 - Attachment is obsolete: true
Attachment #8944817 - Attachment is obsolete: true
(Assignee)

Updated

29 days ago
Whiteboard: sb+
(Assignee)

Updated

29 days ago
Priority: P2 → P1
You need to log in before you can comment on or make changes to this bug.