Andrey Sitnik

Do we really need `strict` but `not autoplace`? I think we added `autoplace` just to avoid major bump.

I like the idea. Do we have Can I Use page for it?

Great. Autoprefixer now in migration to PostCSS 8 process. When I finish it, I will try to add this feature.

Good point. Do we have contrarguments or should we close the issue?

We can use `postcss-preset-env` or a separate PostCSS plugin for non-ideal polyfills.

@felixfbecker what do you think about this section? 

Looks like it is work for separated plugin (like we had for flexbox bugs).

> I think we can do something reasonable with 'smooth' and 'high-quality', but not really 'crisp-edges'. The way '-webkit-optimize-contrast' is currently is via a bilinear filter... which is not really...

Good idea. Do you want to send PR?

1. Find all `.warn(` calls in Autoprefixer sources. 2. Check `Node#warn()` in PostCSS. It should use the node origin. Debug why it is not happening.