- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 1 Jan 2004 21:32:56 +0000 (UTC)
- To: Ernest Cline <ernestcline@mindspring.com>
- Cc: www-style@w3.org
On Thu, 1 Jan 2004, Ernest Cline wrote: >>> >>> It certainly is a lot better than the current practice of using the >>> quirks of existing UA's to try to select what CSS gets used where. >> >> I agree. IMHO the best solution is to simply write to the specs and if it >> breaks in a browser somewhere, tough. That browser should be fixed, not >> the site. > > I was not referring the practice of using CSS hacks to get around > buggy CSS implementations but rather the practice of using CSS hacks > to determine what CSS properties and values a UA supports. Oh. I was not aware anybody did that. Fair enough. > Let me repeat myself, I do not see @property being at all useful for > detecting or avoiding buggy implementations, and that is not what it > is intended for. In that case I'm somewhat confused... can you give an actual use case? Most of the complaints I've heard focus on trying to hide properties from UAs because those UAs handle said properties incorrectly, not on trying to hide properties from UAs that don't support them. Cheers, -- Ian Hickson )\._.,--....,'``. fL U+1047E /, _.. \ _\ ;`._ ,. http://index.hixie.ch/ `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 1 January 2004 16:33:03 UTC