[vinifera]

see, when css 2/2.1 came out, ALL browsers were forced to either obey the standard or get lost
and it was beautiful era

but now, with css 3 all I see are prefixes for different thigs
Opera has -o
Firefox has -moz
Webkit crap has -webkit

and for what ?
why ?

do they render things differently ?

maybe I'm stupid but shouldn't a common standard worth for ALL ?

who and why was behind this ?

[Tripredacus]

The vendor prefixes are designed to allow for backwards compatibility with older browsers. They are meant to be temporary. But I think that as long as these concessions are made to older browsers, the longer they will stay around (hello IE6-7) making developers think they need to keep that compatibility there.

[vinifera]

that doesn't make sense

when css3 was introduced, you have declared how something should behave and what "code" to use
I do understand that sometime due to next version rush browsers partially implement something
but prefixes won't help in that matter

1 unified rule/code for something, either it will work, or it won't ...

I'm so p***ed because all engines have their own set of code different from each other in some areas
instead they should all share 1 unified

[Tripredacus]

I know what you are saying. I don't know why it is so different either across different browsers either.