Closed
Bug 1119253
Opened 10 years ago
Closed 10 years ago
font-selection code should use gfxFontEntry::HasCharacter in preference to TestCharacterMap
Categories
(Core :: Graphics: Text, defect)
Core
Graphics: Text
Tracking
()
RESOLVED
FIXED
mozilla38
People
(Reporter: jfkthame, Assigned: jfkthame)
Details
Attachments
(1 file)
I notice that some of the font-selection code is using the virtual gfxFontEntry method TestCharacterMap, where it should instead use HasCharacter for a more efficient check in the (usual) case where the character map is already loaded.
|
Assignee | |
Comment 1•10 years ago
|
||
Attachment #8545955 -
Flags: review?(jdaggett)
|
|
Assignee | |
Updated•10 years ago
|
Assignee: nobody → jfkthame
Status: NEW → ASSIGNED
|
||
Updated•10 years ago
|
Summary: font-selection code should use gfxFont::HasCharacter in preference to TestCharacterMap → font-selection code should use gfxFontEntry::HasCharacter in preference to TestCharacterMap
|
|
||
Updated•10 years ago
|
Attachment #8545955 -
Flags: review?(jdaggett) → review+
|
|
Assignee | |
Comment 2•10 years ago
|
||
Target Milestone: --- → mozilla38
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•