Open
Bug 1254962
Opened 9 years ago
Updated 3 years ago
[e10s] fonts newly-installed while Firefox is running are not available to content
Categories
(Core :: Graphics: Text, defect, P3)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| e10s | + | --- |
People
(Reporter: jfkthame, Unassigned)
Details
(Whiteboard: gfx-noted)
(Spun off from bug 1167460 comment 3.)
If you install a new font while Firefox is running, the chrome process is aware of it (and it'll show up in the available font list if you check Preferences), but the content process remains ignorant of it until the browser is re-launched.
Without e10s, this works fine: the newly-installed font is fully usable in content.
Either the parent process needs to notify the child to rebuild its font list too, or the child needs to do so directly in response to the WM_FONTCHANGE message from Windows. (But we don't want to do it for every window that receives WM_FONTCHANGE, only once per process.)
|
||
Updated•9 years ago
|
Priority: -- → P2
Whiteboard: gfx-noted
|
||
Comment 2•7 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•