5.
Jun 27, 2007 12:43 PM

in response to:
PCWorld
Safari for Windows: Released and Hacked in a Day
dazzedan above states:
quote:2d8bfc77c7As a developer we have more problems designing around Safari than any other platform.
[/quote:2d8bfc77c7]
This does not make sense, because you should be designing for standards like HTML4, XHTML, CSS, DOM, etc. And once you design for standards, you will find that things work across browsers. Look at Google Gmail, the poster child of a Web application pushes the limits of browser technology, which worked fine in Safari even though it was not designed and tested for it, and even though Gmail gave a warning message that it was an unsupported browser (Opera users also got the same message and it also worked with them, once Opera added the XMLHttpRequest() function).
So either you are going beyond what mainstream standard implementations can provide (a "worst practice" because developer-driven projects sacrifice compatibility in favor of vague usability-oriented goals that in practice are less usable). Or you are making an off-the-cuff slur not substantiated by the facts.
The Safari browser uses the same core engine used by Adobe Apollo and Linux browsers like Konqueror. Early on in the Safari lifecycle, Apple discovered bugs in the core rendering engine and these were fed back into the core codebase, and that was a long time ago. I have used Safari as my principal browser for two years and have not encountered any problems with it. I have developed Web applications that run well on IE, Firefox, Opera, Camino and Safari, and have not seen that Safari deviates from the norm more than the others.