Firefox 3 Rendering Improvements

3 Responses · September 10, 2007

Fire­fox 3 is sche­du­led to be relea­sed later this fall; I haven’t really been follo­wing its deve­lop­ment, but one thing I have heard about and am exci­ted about is its (or, more accu­ra­tely, Gecko’s) new graphics library, Cairo.

Cairo Image Resizing

First I heard that it would resam­ple rather than simply res­cale ima­ges, as demons­tra­ted in the image above (via Acts of Voli­tion).

Later I lear­ned that it will also ren­der fonts more smoothly. I enjoy the soft way pages look in Safari for Win­dows, the result of a dif­fe­rent ren­de­ring engine, Web­Kit, so this is something I’m really loo­king for­ward to. Here’s an exam­ple of Cairo’s font ren­de­ring, as seen in Camino 1.2+ for Mac, via hicks­de­sign:

Cairo Font Rendering

There are very spe­ci­fic rea­sons for the inten­tio­nal dif­fe­ren­ces in these approaches to font ren­de­ring. It’s a mat­ter of per­so­nal pre­fe­rence, and I think my pre­fe­rence will be for Cairo. Some are floo­red by the supe­rio­rity of Web­Kit, and desig­ner Jef­frey Zeld­man makes a solid, objec­tive case for it; others are horri­fied.

Finally, Gecko’s non-standard CSS attri­bute –moz-border-radius, a pre­cur­sor to CSS3’s border-radius attri­bute, will make image-less roun­ded div cor­ners easy and pretty (via Acts of Voli­tion):

Cario Border Radius

I would have pos­ted screenshots of my own, but I don’t trust these alpha builds not to eff things up.

Here’s an exam­ple of Cairo’s font ren­de­ring, as seen in Camino 1.2+ for Mac, via hicksdesign:

If you take the time to read the com­ments on the hicks­de­sign post you link to, you’ll notice that Camino’s ren­de­ring was due to a bug. To quote David Smith:

Jon: could you put a note about the bold ren­de­ring being due to a Cairo bug (not synthe­si­zing a bold font, spe­ci­fi­cally)? It seems disho­nest to leave it up there as a shi­ning exam­ple when it’s actually incorrect.

If you com­pare the ren­de­ring of Camino 1.5, which as the ver­sion num­ber sug­gests is newer than Camino 1.2+, on Ama­zon UK to that of the screenshot you pos­ted, you’ll notice that it now ren­ders vir­tually iden­ti­cally to the Camino 1.0 and Safari 2.0 screenshots. The rea­son for this? It’s the correct ren­de­ring! I agree that the buggy ren­de­ring does look nicer, but it’s a result of the ina­bi­lity to synthe­size a bold variant of a font when the font has no native bold itself. You could get an iden­ti­cal ren­de­ring in Camino 1.0 and Safari 2.0 if you disa­bled the bold sty­ling on that navi­ga­tio­nal element.

Sprea­ding misin­for­ma­tion really isn’t cool.

Mark Rowe · September 10, 2007

^
I
I
lol what a tool

Sumner · November 26, 2007

by the way that arrow is poin­ting to ever­yone above it.

Sumner · November 26, 2007

Leave a Comment or Subscribe