Not really. The prefixes allow vendors to do experimental stuff without creating (as much) of a backwards compatiblity problem before things standardize. If you don't like it, use a preprocessor:

* http://sass-lang.com/ * http://lesscss.org/ * http://learnboost.github.com/stylus/

The last one is the most promising since it can be made to look exactly like standard css, but it's really rough right now.

Sass, at least with its default SCSS syntax, is a strict superset of CSS3 so it's a good place to start. Your existing CSS files can be processed by Sass without changes.

Combined with some of the great mixins provided with Compass: http://beta.compass-style.org/reference/compass/css3/transfo..., you can eliminate many of the vendor specific declarations.

They all either are or can be strict supersets of CSS3. What separates stylus is that you can write valid, non-superset CSS3 and invoke the appropriate functions/mixins:

    @import css3

    #transparent {
        opacity: 0.6;
    }

    ----

    #transparent {
      opacity: 0.6;
      -ms-filter: "progid:DXImageTransform.Microsoft.Alpha(Opacity=60)";
      filter: progid:DXImageTransform.Microsoft.Alpha(Opacity=60);
    }

That's input/output in stylus. This uses an `opacity` mixin defined that's being invoked without the optional parentheses and with the optional colon+semicolon.

I have the beginnings of the Compass CSS3 library that's on hold while TJ fixes bugs and adds features to cover edge cases. The eventual goal is the ability to write straight CSS3 and have everything work.

Yes, once transforms enter CR.

Note, by the way, that right now -moz-transform and -webkit-transform have different syntax, so "consolidation" involves deciding which syntax to standardize on.