-
-
Notifications
You must be signed in to change notification settings - Fork 79k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add grunt-autoprefixer to grunt tasks #12452
Comments
I think no. Bootstrap doesn't need all the prefixes. |
autoprefixer doesn't just add all the prefixes, it actually can be tuned very fine. |
I know, but is it really required? It disallows removal of specific prefix, when caniuse becomes outdated. |
caniuse is updated every couple of days, I don't think that we'd need to worry about that. |
Ok then. We have to try. :) |
I'm down with it. I'd love for mixins to be only for code snippets and not prefixing. We can deprecate any of those mixins and switch to the autoprefixing, but I wonder if there would be any kind of conflict in that? Would also be super cool to see a list of what can be switched over and what can't. |
Done! #12670 |
🎆 🎉 🎊 |
Instead of maintaining mixins for things like box-shadow and transition - we should just implement as part of our build process via this grunt task for autoprefixer. It runs off of the info from http://caniuse.com which makes it much easier to maintain proper vendor prefixes. Less mixins seems worth the price of admission alone.
The text was updated successfully, but these errors were encountered: