My development path does not factor in the amount of users which may be utilizing any particular browser. It's a path designed to create a site that works in
all of them. What difference does it make how many users are launching a particular browser? Even if the user base is 1.6% if 10 people visit a site I design 2 of them getting errors is unacceptable to me. 100% compatibility across browsers and platforms is always my goal. The point is that people
are using those browsers. The amount or users is quite irrelevant. If you ran a local candy store, would you throw out 2 of every 10 customers?
Quote:
|
One would assume that a 'Standard' would be indocturned across more than just a single browser.
|
That is what "standard" means. And this is why Safari and Firefox are dramatically similar in most cases. It's IE that is not a standards compliant browser. IE7 is closer than IE6 but both are far from being standards compliant.
I realize that Safari has a small user base, but honestly it is by far the most standard compliant browser out there (and the only one that has color management built in.) By coding with the most compliant browser available you learn to code properly, then adjust for the browser issues. In 99% of the cases you'll find coding for Safari and Firefox will be seamless. There are very rare occasions where you must choose between one or the other for a particular code structure, but in general they are pretty much the same. If you don't want to code for Safari first, then code for Firefox first. But never, ever code a site using IE as the preview browser, ever.
As for testing IE6 and 7.. dual boot system. Or a Mac with Parallels and two Win installations.