W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

Re: Acceptable for CSS to add a "window.CSS" global?

From: Cameron McCormack <cam@mcc.id.au>
Date: Sun, 19 Aug 2012 11:03:19 +1000
Message-ID: <50303B57.5080100@mcc.id.au>
To: Chaals McCathieNevile <w3b@chaals.com>
CC: Ian Hickson <ian@hixie.ch>, "Tab Atkins Jr." <jackalmage@gmail.com>, public-webapps <public-webapps@w3.org>
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.
Received on Sunday, 19 August 2012 01:03:49 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:54 GMT