I totally agree, I think that a recognised set of browser support standards would be very useful.
As you pointed out, Yahoo set the pace or at least popularised the idea of graded browser support (gbs), I think the BBC’s Browser Support Standards Work Group have taken it further with clearer definitions of those levels of support:
I think having a common set of support level definitions would help manage client/stake-holder expectations.
Andy Clarke has written some excellent posts recently on browser support and related issues with client/stakeholder expectations, these being very good:
Paul Michael Smith
I totally agree, I think that a recognised set of browser support standards would be very useful.
As you pointed out, Yahoo set the pace or at least popularised the idea of graded browser support (gbs), I think the BBC’s Browser Support Standards Work Group have taken it further with clearer definitions of those levels of support:
Browser Support Standards v3.3
I think having a common set of support level definitions would help manage client/stake-holder expectations.
Andy Clarke has written some excellent posts recently on browser support and related issues with client/stakeholder expectations, these being very good:
Time to stop showing clients static design visuals
Five CSS design browser differences I can live with
Maybe along with ACID3, a standard support definition could be hosted on Wasp.
Nice post Jeremy.