W3C home > Mailing lists > Public > www-style@w3.org > November 2007

Re: Proposal of @ua

From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Date: Fri, 23 Nov 2007 08:39:24 +0000
Message-ID: <474691BC.6030600@googlemail.com>
To: David Woolley <forums@david-woolley.me.uk>
CC: "www-style@w3.org" <www-style@w3.org>

David Woolley wrote:
> 
> Benjamin Hawkes-Lewis wrote:
>>
>>
>> CSS implementations already have code to determine whether a property 
>> and its value are supported or should be ignored. So rather than UA 
>> detection, how about considering some sort of feature detection for CSS?
> 
> This would only detect the marketing claim for the feature. The feature 
> might actually be incompletely or wrongly implemented.  Getting false 
> claims fixed is likely to a low priority in any change control process.
> 
> Marketing claims tend to be optimistic and based on reading the 
> standards in the favour of the implementor.

Indeed, but note that's true for JS too. For example, you can detect 
getElementById but you can't be sure it won't get elements by NAME too 
(as the JScript implementation does). But JS feature detection is still 
generally preferable to browser detection. But perhaps one would need 
both to work around known broken implementations.

--
Benjamin Hawkes-Lewis
Received on Friday, 23 November 2007 08:39:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:56 GMT