Bug 67996 – WebFont followed tiny monospace text displays weird

• Status: RESOLVED
• Resolution: FIXED
• Component: Text

[Kenichi Ishibashi]

Text using webfonts sometimes looks weird. See http://crbug.com/59033 in details.  I confirmed this could occur with Safari and Chromium mac.

[Kenichi Ishibashi]

Created attachment 107162 [details]
Patch

I was told that saving and restoring the graphics state is relatively expensive. Is it possible to save and restore the specific attribute that’s changing here?

[Kenichi Ishibashi]

Thank you for taking a look.

(In reply to comment #2)
> I was told that saving and restoring the graphics state is relatively expensive. Is it possible to save and restore the specific attribute that’s changing here?

I'm not sure which attributes should be saved and restored because wkSetCGFontRenderingMode() is black-box to me.. I'd appreciate if someone could give advice on this. (I might well have to brute force investigation, though).

[Darin Adler]

Comment on attachment 107162 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=107162&action=review

> Source/WebCore/platform/graphics/mac/FontMac.mm:212
> +        CGContextSaveGState(cgContext);

We need to know more before we make this code change.

Doing a complete CGContextSaveGState can be an expensive way to save and restore state. While complete, it has a high performance cost. I believe that’s why we don’t use it to preserve the setting of CGContextSetShouldSmoothFonts.

An alternative is to come up with a different way of dealing with the state in question. For each piece of state we can decide to either:

    1) Set it each time, or
    2) Restore it to the previous state with an explicit function call, or
    3) Restore it to a “neutral” state with an explicit function call.

For font size we might choose to do (1). Each piece of code drawing any text would have to set the font size and not assume that it’s set to any particular value beforehand.

For font rendering mode we might choose to do either (1) or (3).

I am not going to say review- because I am not certain that a complete save/restore is too slow, but I suspect it is.

I think the best approach here would be to always set the rendering mode. wkSetCGFontRenderingMode() will behave correctly if passed a nil font.

[Darin Adler]

Comment on attachment 107162 [details]
Patch

review-; please try Mitz’s suggestion of calling wkSetCGFontRenderingMode every time

[Kenichi Ishibashi]

Created attachment 107263 [details]
Patch V1

[Kenichi Ishibashi]

Hi Darin, mitz,

Thank you so much for your help.  Calling wkSetCGFontRenderingMode() always solves the problem.  Revised the patch.

[WebKit Review Bot]

Comment on attachment 107263 [details]
Patch V1

Clearing flags on attachment: 107263

Committed r95070: <http://trac.webkit.org/changeset/95070>

[WebKit Review Bot]

All reviewed patches have been landed.  Closing bug.

*** Bug 28915 has been marked as a duplicate of this bug. ***

[David Harrison]

rdar://10259221