RE: Selecting for features

>Certainly, but that's already an issue. We already have browser vendors claiming full compliance when that's not necessarily the case; they just do it in marketing 
> rather than in code. 

That the code returns a match only reflects the developers' belief that they have implemented the feature properly. That is not the same as marketing collateral which no JS code or stylesheet can easily depend on. One can argue that it's not fundamentally any different than what authors already do using libraries such as Modernizr. 
It's quite possible that a browser will make the wrong claim every now and then but that is only a new incentive to fix the underlying bugs as every declaration block they erroneously match could make web pages look worse in their UA. 

That the mechanism may fail in some cases in practice is no good reason to not try to come up with a standard solution for a very popular feature request imo.

Received on Saturday, 10 July 2010 23:54:29 UTC