Thoughts on Autoprefixer

[claviska]

Now that we switched to PostCSS for minification, it may be time to consider using Autoprefixer too. I don't think there's anything that's unsupported in target browsers at the moment, but for future use it's probably a good idea.

Not sure how much weight this will add to the lib — probably not too much.

I think the target should be last two browser versions. Any other options I should consider?

Thoughts?

[malchata]

this is a very easy add, but the hard part with autoprefixer is deciding what query you want to use. Optionally, you could leave it prefixless and advise users to process it on their own, but that makes it less friendly out of the box.

[claviska]

I was hoping you'd chime in on this, thanks :)

It may be worth experimenting with at least, even if we decide against it after.

Users who want IE support (any version) need to use Myth for handling CSS vars. Myth also does prefixing, so basically we don't need to worry about folks who want IE support.

Knowing that, I'm OK with using the last two versions preset. Is there anything else I'm not thinking about in terms of Autoprefixer? Seems pretty straight forward, but I've only used it in as a gulp plugin with a couple basic settings before.

[malchata]

This is the query I tend to use on my projects:
"last 2 versions", "> 5%", "ie > 10", "iOS >= 8"

That said, I haven't updated it in some time, but I feel this is reasonable. I can add it if you want.

[claviska]

If you wanna take a stab at it I'd love to see the result. It would give me more confidence knowing it will resolve a lot of edge cases as we move toward stable.

[claviska]

Merged with #10