Comments on: Firefox 3 Rendering Improvements http://www.kilobitspersecond.com/2007/09/10/firefox-3/ A blog about Destroyer, foobar2000, and Last.fm. Wed, 20 Aug 2008 02:31:17 +0000 http://wordpress.org/?v=2.6 By: Sumner http://www.kilobitspersecond.com/2007/09/10/firefox-3/#comment-2817 Sumner Mon, 26 Nov 2007 08:17:27 +0000 http://www.kilobitspersecond.com/2007/09/10/firefox-3/#comment-2817 by the way that arrow is pointing to everyone above it. by the way that arrow is pointing to everyone above it.

]]> By: Sumner http://www.kilobitspersecond.com/2007/09/10/firefox-3/#comment-2816 Sumner Mon, 26 Nov 2007 08:15:29 +0000 http://www.kilobitspersecond.com/2007/09/10/firefox-3/#comment-2816 ^ I I lol what a tool ^
I
I
lol what a tool

]]> By: Mark Rowe http://www.kilobitspersecond.com/2007/09/10/firefox-3/#comment-1972 Mark Rowe Tue, 11 Sep 2007 03:08:09 +0000 http://www.kilobitspersecond.com/2007/09/10/firefox-3/#comment-1972 <blockquote> Here’s an example of Cairo’s font rendering, as seen in Camino 1.2+ for Mac, via hicksdesign: </blockquote> If you take the time to read the comments on the hicksdesign post you link to, you'll notice that Camino's rendering was due to a bug. To quote David Smith: <blockquote> Jon: could you put a note about the bold rendering being due to a Cairo bug (not synthesizing a bold font, specifically)? It seems dishonest to leave it up there as a shining example when it’s actually incorrect. </blockquote> If you compare the rendering of Camino 1.5, which as the version number suggests is newer than Camino 1.2+, on Amazon UK to that of the screenshot you posted, you'll notice that it now renders virtually identically to the Camino 1.0 and Safari 2.0 screenshots. The reason for this? It's the correct rendering! I agree that the buggy rendering <em>does</em> look nicer, but it's a result of the inability to synthesize a bold variant of a font when the font has no native bold itself. You could get an identical rendering in Camino 1.0 and Safari 2.0 if you disabled the bold styling on that navigational element. Spreading misinformation really isn't cool.

Here’s an example of Cairo’s font rendering, as seen in Camino 1.2+ for Mac, via hicksdesign:

If you take the time to read the comments on the hicksdesign post you link to, you’ll notice that Camino’s rendering was due to a bug. To quote David Smith:

Jon: could you put a note about the bold rendering being due to a Cairo bug (not synthesizing a bold font, specifically)? It seems dishonest to leave it up there as a shining example when it’s actually incorrect.

If you compare the rendering of Camino 1.5, which as the version number suggests is newer than Camino 1.2+, on Amazon UK to that of the screenshot you posted, you’ll notice that it now renders virtually identically to the Camino 1.0 and Safari 2.0 screenshots. The reason for this? It’s the correct rendering! I agree that the buggy rendering does look nicer, but it’s a result of the inability to synthesize a bold variant of a font when the font has no native bold itself. You could get an identical rendering in Camino 1.0 and Safari 2.0 if you disabled the bold styling on that navigational element.

Spreading misinformation really isn’t cool.

]]>