[Webkit-unassigned] [Bug 69609] 'optimiseLegibility' text rendering issue OSX

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Oct 8 23:26:06 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=69609





--- Comment #10 from vernnobile at gmail.com  2011-10-08 23:26:06 PST ---
Many thanks. 
Under latest nightly builds of Webkit and Google Canary, the issue is now fixed :) text rendering is now optimised, and comparable to Gecko.

Re: Coda font. this font has no kerning pairs for lowercase characters. Hence why it's letter spacing doesn't tighten under 'optimizeLegibility'. However, does optimizeLegibility apply any auto-hinting or that would explain the looser (but better?) spacing under optimizeLegibility?

(In reply to comment #9)
> Note that Gecko on OS X has 'optimizeLegibility' turned ON by default (and you can't turn it off). On the other hand, Opera doesn't support that property, so far.
> 
> See https://developer.mozilla.org/en/CSS/text-rendering for a description of the property. Is there a similar Apple doc ? I may have missed it…
> 
> That being said, 
> * I see a slight difference - improved (!) rendering – on the latest Webkit compared to Safari 5.1
> * I see virtually no difference between the latest WebKit and Fx 7 and Gecko nightly builds. The spacing between words is slightly looser on Gecko – it looks like Webkit tightens the white-space slightly whereas Gecko does not.
> 
> * the Coda font has a weird behaviour in WebKit - the spacing is looser with 'optimizeLegibility' than without. I would expect the opposite. The text run without optimisation on WebKit looks the same as Gecko (which has optimisation ON by default)
> 
> Tested on 10.6.8 - took some screenshots and overlayed them in Photoshop.

-- 
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