DescriptionSimpleFontData::fillGlyphPage should not set zero for missing glyphs
From r171835, we call fillGlyphPage() multiple times on a glyph page
when initializing a page for SegmentedFontData. It introduced a bug
where glyph fallback for overlapping unicode ranges does not work
correctly, because fillGlyphPage() may overwrite zero for missing glyphs.
Since GlyphPage's constructor does zero-clear, there is no need to
set zero for missing glyphs.
BUG=none
TEST=fast/css/font-face-unicode-range.html,svg/custom/svg-fonts-segmented.xhtml
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=172107
Patch Set 1 #
Total comments: 2
Patch Set 2 : fix expectation #
Messages
Total messages: 7 (0 generated)
|