|
Yes Jolt! I wholeheartedly agree that you should NOT code for IE first.
As for Safari, i have no experience with it's differences from firefox... every site i've done seems to work just fine in both. (Although i have encountered differences between the mac and pc versions of safari with padding)
My point was, and Gjbphp has eluded to it, that you can spend hours tracking down a solution to even 1 disrepancy and may never have a vistor to the site use Safari.
In fact more people use mobile browsers built into devices such as Blackberries, Cell phones, and iTouch Ipods than use Safari but most developers do not code for mobile devices unless their is a perceived need or a client requests it.
That said, if a person does want to ensure 100% browser compatibility regardless of the time required, then absolutley your approach makes complete sense and i would not have known to start with Safari... i have always coded for Firefox fixed for IE and checked it in Safari.
When you say Safari is the most Standard Compliant browser, to which standard does it comply? The W3 consortium Standard or the working standard (which seems to be non-standard)?
|