With the recent arrival of Firefox 2.0 and Internet Explorer 7, I updated the "browser matrix" that I would aim to develop for on a regular basis "as standard" (assuming use of a doctype and validating against it):
[ul]
[li]Internet Explorer 6, 7 (Win)[/li]
[li]Netscape 8.1 (Win)[/li]
[li]Firefox 1.5, 2 (Win/Mac)[/li]
[li]Opera 8, 9 (Win/Mac)[/li]
[li]Mozilla 1.7 (Win/Mac)[/li]
[li]Safari 2.x (Mac)[/li]
[/ul]
I'm expecting that within a few months very few users will be running IE5x, so I've cast it aside - even though IE 5.5 is still in common use (almost all IE 6 CSS changes work in the same way for IE 5.5 so it's hardly a big deal). Development of Mozilla Suite ended a while back - but it's still high on the radar for browser stats (and it's pretty much a freebie if you get it right in Firefox anyway).
I develop in Firefox (Win) during the day - and find that very little effort is required to "tweak" IE 6 into submission (usually as simple as using a conditional comment to include an overriding css file). All the other browsers on the list just kind of fall off the back of good JS and CSS implementation.
I don't test on these browsers constantly, but certainly at key points of development (especially when setting up initial CSS templates).
I've been asked to support some strange combinations in recent contracts... but inevitably I find these lists do not reflect the profile of their vistor. I would be interested in hearing what others choose to support "as a standard" (rather than because of a specific request from the client).
Cheers,
Jeff
[tt]Jeff's Page @ Code Couch
[/tt]
What is Javascript? FAQ216-6094
[ul]
[li]Internet Explorer 6, 7 (Win)[/li]
[li]Netscape 8.1 (Win)[/li]
[li]Firefox 1.5, 2 (Win/Mac)[/li]
[li]Opera 8, 9 (Win/Mac)[/li]
[li]Mozilla 1.7 (Win/Mac)[/li]
[li]Safari 2.x (Mac)[/li]
[/ul]
I'm expecting that within a few months very few users will be running IE5x, so I've cast it aside - even though IE 5.5 is still in common use (almost all IE 6 CSS changes work in the same way for IE 5.5 so it's hardly a big deal). Development of Mozilla Suite ended a while back - but it's still high on the radar for browser stats (and it's pretty much a freebie if you get it right in Firefox anyway).
I develop in Firefox (Win) during the day - and find that very little effort is required to "tweak" IE 6 into submission (usually as simple as using a conditional comment to include an overriding css file). All the other browsers on the list just kind of fall off the back of good JS and CSS implementation.
I don't test on these browsers constantly, but certainly at key points of development (especially when setting up initial CSS templates).
I've been asked to support some strange combinations in recent contracts... but inevitably I find these lists do not reflect the profile of their vistor. I would be interested in hearing what others choose to support "as a standard" (rather than because of a specific request from the client).
Cheers,
Jeff
[tt]Jeff's Page @ Code Couch
[/tt]
What is Javascript? FAQ216-6094