Re: vendor prefixes considered harmful (was: vendor prefix properties diverging from official properties)

I agree that vendor prefixes require attention. If I wish to use an 
experimental property, I should not have to declare 4 or 5 variations of 
it (and it's 4 or 5 *now*, what happens when additional rendering 
engines are developed?).

As mentioned by more than one person in the previous discussion 
regarding this topic, a single prefix for work-in-progress properties 
could be defined. For example:

-border-radius: 10px;     (or --, or x-, etc.)

This would be used by all vendors who have an implementation matching 
the current WD.

A vendor prefix would then be used in the following two cases:

1. Proprietary properties (no standard exists).
2. Alternative syntax or behavior of a property (differing implementation).

I just think that this is ridiculous:

     border-top-left-radius: 8px;
     border-top-right-radius: 8px;
     -khtml-border-radius-topleft: 8px;
     -khtml-border-radius-topright: 8px;
     -moz-border-radius-topleft: 8px;
     -moz-border-radius-topright: 8px;
     -webkit-border-top-left-radius: 8px;
     -webkit-border-top-right-radius: 8px;

.... just to round the top of an element. If this wasn't a CR, there 
might well have been 4 extra declarations for Opera & IE. That's *6* 
declarations for every property!?

Just my thoughts.

Glen.

P.S. Why does border-radius: 5px 10px; affect tl/br and tr/bl, and not 
tl/tr and bl/br or tl/bl and tr/br? It seems like the least useful 
alternative.