W3C home > Mailing lists > Public > www-style@w3.org > September 2005

Re: Browsers will never get it right [was Re:Blocked-base parsing?]

From: Kornel Lesinski <kornel@osiolki.net>
Date: Wed, 14 Sep 2005 14:43:00 +0100
To: "Ian Hickson" <ian@hixie.ch>
Cc: www-style <www-style@w3.org>
Message-ID: <op.sw3hpyq84suneb@idlaptop02.mshome.net>

On Wed, 14 Sep 2005 13:24:20 +0100, Ian Hickson <ian@hixie.ch> wrote:

> Yes, that's quite possible. However, the proposed feature wouldn't
> actually help with this case, since you'd end up with browser X claiming
> support for border-radius despite a fatal (but unnoticed when the browser
> shipped) bug. Or some similar thing.

Look:

* Browsers should ignore selectors which they don't support, but some have  
fatal bugs and don't.
* Browsers should ignore properties which they don't support, but some  
have fatal bugs and don't.
* Browsers should ignore @required blocks which they don't support, but  
because some may have fatal bugs and don't, @required is useless and let's  
not bother at all.

Don't you think that it's unfair/too idealistic to consider @required  
doomed because of browser bugs?

It's impossible to create mechanism that will effortlessly ensure perfect  
rendering, in all browsers, current and future, despite their bugs and  
malicious efforts of marketing deparments, but @required is as close as  
you can get.

CSS1 properties were pretty independent, and per-property fallbacks were  
ok, but in later levels many groups properties work together, so there is  
neccessity for per-group fallbacks.

-- 
regards, Kornel Lesiński
Received on Wednesday, 14 September 2005 13:40:49 GMT

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