flickr-free-ic3d pan white

Google Chrome vs Safari 3.1

One of the first things I tried out after installing the brand new Google Chrome was my own upcoming site's holding page — found at — as it has some CSS transitions and miscellaneous CSS3 properties in it. With Google Chrome using Webkit as the rendering engine (to a point), I was curious to see how it would perform on up-and-coming CSS awesomeness.


Sadly, it seems the Webkit build that Google Chrome uses has been mutilated to an extent: the text-shadow property has been stripped out (Why?!) and, worse, the CSS border-radius rendering is not anti-aliased (Why?!?!).


If anyone knows what the reason for these changes is, please leave a comment.



Here is the UA String (navigator.userAgent result) for Google Chrome:


Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/ Safari/525.13



So it turns out that because Google Chrome uses Skia, a different graphics engine than employed by Webkit/Safari, various rendering features are not yet or not yet fully implemented. Shadows, anti-aliasing and certain opacity and alpha-transparency combinations are the most notable features currently missing. Google plans to add these but has not given time estimates.

6 faves
Uploaded on September 2, 2008