Welcome to WebmasterWorld Guest from 220.127.116.11
Forum Moderators: open
If you want a list of bugs currently affecting Safari, you should check out the WebKit development website:
Also take a look at Safari's useragent...
Mozilla/5.0 (Macintosh; U; PPC Mac OS X; nl-nl) AppleWebKit/417.9 (KHTML, like Gecko) Safari/417.8
Besides the fact that it identifies itself as the Mozilla browser (which will never reach 5.0 since Mozilla 1.7x was the version before it morphed in to SeaMonkey) it also identifies itself as Gecko! This is EXTREMELY obnoxious and forces Gecko detection to depend on "rv:" string.
Since I do not have a Mac I can not test Safari out to greater extents.
Gecko and Presto continue to be the best rendering engines.
Thanks for the link encyclo, they will be hearing from my shortly. ;)
...something that is 'known to work' in Firefox but not in Safari. I'm not talking about bad code either.
There plenty of HTML/CSS techniques that work in Firefox but not Safari, but most of them are indeed caused by the fact that Safari has a more strict approach to standards. Would you qualify that as "bad code" on the part of Firefox? I don't know that I would necessarily, but I suppose the case can be made that if you CAN write the code so that it works in Firefox AND Safari, then failing to do that is bad coding.
May I ask why you want to know? If you're planning on writing a Safari-bashing (or Firefox-bashing) essay or something, I guess I can see the point. I don't know that you'll get a reputable answer without divulging your agenda.