Hi everybody, Even though Chrome is based on Webkit, Chrome actually uses another graphics/rendering engine (the drawing layer) called Skia (source code: http://src.chromium.org/viewvc/chrome/trunk/src/skia/). A bit like the javascript engines, Google didn't use webkits' javascript engine (Sqirrelfish or whatever they had before it) but developed one themselves; V8...
Skia came from an acquisition made by Google in 2005 of a small startup specialising in Mobile graphics ( http://localtechwire.com/business/local_tech_wire/news/story/1126258/). Skia seems to be heavily used in Android and is now part of Chrome as well. Thus there are differences in rounded borders where the antialiasing doesn't work so well, fonts that are smoothed differently and shadows are rendered incorrectly. This was the case a few monts ago, but I haven't tested it recently; it might be better now. I've heard about opacity and png problems (rounding alpha values to 1bit) but I haven't noticed any problems with that. I'm not sure why Google decided to use Skia, maybe some proprietary bits from Quartz or from Safari that could not be used, maybe they just wanted to use their own technology... Maybe somebody else here knows about it ? Cheers, Johan Douma johando...@gmail.com 2009/1/8 Simon Pascal Klein <kle...@klepas.org> > I think this comes down more to which font rasterisation engine a system is > using. I don't think Safari on Windows for example has full access to AAT > and Quartz and thus will render type using ClearType and GDI on Windows. Add > Firefox into the mix which uses Cairo and you'll get different results > again, which are easily visible (for example) when comparing how Firefox > using Cairo and ATSUI renders fonts that don't have their own small-capitals > and thus must downsize capitals to a small-cap scale (traditionally the > x-height of the face) and how Safari handles the same thing. (Safari, I find > does this better—a good font to test this with is Georgia which sadly lacks > proper real small-capitals.) > > To fix layout issues with content running outside your boxes use absolute, > fixed and relative positioning instead of floats, eg: > > div#container { > position: relative; > width: 100%; > } > > div.content_primary { > width: 60%; > left: 0; > } > > div.content_secondary { > width: 40%; > left: 60%; > } > > This way you can also quickly switch your columns around without touching > your markup; add absolute positioning to the column that appears first in > the markup (likely to be content_primary) and swap the left property indent. > > Hope any of this helps. > > > —Pascal > > > On 08/01/2009, at 4:36 PM, Jens-Uwe Korff wrote: > > Hi experts, >> >> I'm running into big rendering differences between Google Chrome and >> Safari 3.1/PC. They are said to render pages the same, given that >> they're using the same Webkit engine. >> >> The differences seem to be mainly due to the different font rendering. >> Safari's fonts are way smaller, hence my boxes are smaller and shift up, >> breaking the layout. >> >> Anyone knows why this is so? Is there a workaround, i.e. a Safari-only >> CSS hack? >> >> Cheers, >> >> Jens >> >> The information contained in this e-mail message and any accompanying >> files is or may be confidential. If you are not the intended recipient, any >> use, dissemination, reliance, forwarding, printing or copying of this e-mail >> or any attached files is unauthorised. This e-mail is subject to copyright. >> No part of it should be reproduced, adapted or communicated without the >> written consent of the copyright owner. If you have received this e-mail in >> error please advise the sender immediately by return e-mail or telephone and >> delete all copies. Fairfax does not guarantee the accuracy or completeness >> of any information contained in this e-mail or attached files. Internet >> communications are not secure, therefore Fairfax does not accept legal >> responsibility for the contents of this message or attached files. >> >> >> ******************************************************************* >> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm >> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm >> Help: memberh...@webstandardsgroup.org >> ******************************************************************* >> >> > --- > Simon Pascal Klein > Concept designer > > (w) http://klepas.org > (e) kle...@klepas.org > > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: memberh...@webstandardsgroup.org > ******************************************************************* > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
