This is why I use Sass and Compass.

I’ll be the first to admit: I don’t really get how it all works. The standards process, the politics… I think I get the general idea, but that’s not really important. I know what vendor prefixes are for, and I’m tired of using them 4 times over with the same value. When 4 competitive companies/organizations use the same syntax for something, I’d call it a standard.

I realize you may have different criteria, but perhaps this could be considered, if only for “point” releases of the spec.

Sorry if I don’t really get it, still love you crazy cats.

Please don’t implement Webkit prefixes. The very idea is absurd, goes against the entire reason for having CSS prefixes, and makes me a sad panda. What happens if/when Webkit decides to change the implementation of -webkit-text-size-adjust? They’re completely in their right to do so, as it’s their recommendation. That’s why it has a -webkit in front of it.

If you want developers using more of your prefixes, then you probably need to offer more innovative specs, do a better job marketing your features, or simply gain more marketshare. We don’t throw -webkit in front of stuff because it’s fun, we do it to target the most powerful/prevalent mobile browsers, animate stuff (smoothly, ahem), or polish UI to show off for fellow Mac-loving, Webkit-using, designers.

Stealing prefixes is cheating and is going to screw up a nice little system. Please don’t.

Update: In case you aren’t familiar with the discussion, see here.