Chaals McCathieNevile:
Frankly, I am deeply sceptical that the CSS group has managed to solve the social problem sufficiently well to make the technical solution noticeably different from hasFeature.
I think the biggest difference between hasFeature and supportsCSS is that the implementation of the former, for a given feature string, would be completely independent of the feature it is testing for. So someone must make a judgement at some point about whether to return true for a given feature string. With supportsCSS, I would imagine that it would return true or false by passing the string along to the CSS parser, so you would be much more likely to get an accurate answer out of it and there'd be no need for someone to make the judgement call.
