On Fri, 12 May 2006, axlq wrote:
I wonder why "in its own way" was necessary. Why didn't the FF
authors just support the CSS3 border-radius instead of inventing
some new and browser-specific attribute called "-moz-border-radius"?
Bit of history for you. MSIE3 implemented some CSS(1) when it was
still in draft. And misbehaved royally when the actual specification
came out, and some of us started to code to it. Misbehaved so badly
that we had to find ways of hiding the CSS from that thing.
CSS3 is still in draft. Various developers are getting practice with
implementing the drafts, without falling into the trap of presenting
them as if they were standard CSS. This is *good* - don't knock it.
The CSS specification is very clear about how to handle undefined
properties. We can happily code -moz-whatever and -opera-whatever and
-konq-whatever... to call out whatever their developers care to
implement experimentally. Other browsers are required to calmly
ignore what they don't understand. When CSS3 is final, they can
introduce the new standard property names, and phase out the
experimental ones, with a decent overlap, causing a minimum of
disruption.