7 Answers
7

I've noticed Safari handles Asian characters better than Chrome.
Also Chrome and Safari rely on the same Webkit for rendering pages, but their Javascript engines are totally different, so if you use Javascript in your pages you need to check both.

Safari uses 'mac' fonts, but Chrome would use 'Windows' fonts. I've noticed that there can sometimes be problems where using a font like Arial, it shows up fine in firefox/chrome/ie, but on Safari, it can cause a line to wrap because the font is slightly bigger.

Something may be wrong if your site depends on pixel-perfect accuracy (not talking about CSS standards here), especially with fonts... HTML was designed to simply not care what was done with the rendering. Regardless, you may forget to include "sans-serif" in your font-family list or something.
–
stragerDec 17 '08 at 5:12

"For 99% of the problems"? Then, that would be no, unless you're relying on statistical sampling rather than exhaustive testing (which isn't necessarily a bad thing, but you should be aware of its limitations). Still, if 99% is right, that's pretty damn good statistical sampling...
–
paxdiabloDec 17 '08 at 4:41

Just for the record, I've reworded the question now, so this "yes" answer actually means "no, you don't need to test Safari".
–
nickfDec 17 '08 at 15:01

Oh, you wanted more detail? Simply, Chrome and Safari have a lot of different features in their implementations, and Safari is pretty widely used. If you expect the general public, and particularly those of us who work on Macs, to use your application, it would behoove you to test in the Safari browser.

In a word, No. You can't assume that because it works in one it will definitely work in all cases in the other. Sure, 99% of the time, it might be the same - but 99% isn't 100% - at least, it wasn't last time I checked. Call me a pedantic git if you like.