[Webkit-unassigned] [Bug 41599] optimizeLegibility doesn't play nice with fonts that do not have a space glyph

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jul 5 09:43:04 PDT 2010


mitz at webkit.org changed:

           What    |Removed                     |Added
            Summary|optimizeLegibility doesn't  |optimizeLegibility doesn't
                   |play nice with fonts that   |play nice with fonts that
                   |use the space glyph for     |do not have a space glyph
                   |ZERO WIDTH SPACE            |

--- Comment #2 from mitz at webkit.org  2010-07-05 09:43:04 PST ---
Further debugging shows that the problem is that the font doesn’t map the SPACE character to a glyph. WebKit substitutes the space glyph from the next font in fallback order, but in some code paths, WebKit uses the cached space width from the font itself, which is bogus. This discrepancy is what’s causing the incorrect line breaking.

Specifically, in RenderBlock::findNextLineBreak(), the initialization of wordTrailingSpaceWidth should probably be changed to measure a space character instead of using the cached space width.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list