-
-
Notifications
You must be signed in to change notification settings - Fork 188
Remove some not future css
plugins from next major release
#375
Comments
Why not. Curious to know what people want. |
I did not get to participate in this poll, but I would have voted in favor of removing these not future css plugins. Congrats on getting so many participants. It looks like a large majority wanted them gone. |
Also, you might want to remove pleeease-filters from #374 (comment). Firefox has supported gradients since early 2015 in version 35 (we are on 53). From the pleeease-filters docs:
Confirmed by caniuse. |
How about IE 11 support? |
The future of |
I’ve pinged the csswg or anyone who can spare time to update this db with accurate information. https://twitter.com/jon_neal/status/863108278666047488 If we get that repo in order as a source of truth, we can very intelligently update the feature set in cssnext, and even add stages/env in the future. |
IE does not support SVGs filters. |
I'd also suggest removing See comments by tabatkins on ianstormtaylor/css-color-function#35. |
If the name is locked to |
Possibly resolved by #445 |
|
postcss-color-rgba-fallback
rgba(153, 221, 153, 0.8)
->#99DD99
http://caniuse.com/#feat=css3-colors (IE 8-)
postcss-pseudoelements
:before {}
->::before {}
http://caniuse.com/#feat=css-gencontent (IE 8-)
pixrem
2.5rem
->80px
http://caniuse.com/#feat=rem (IE 10-)
Good plugin pack for this plugins: https://github.com/jonathantneal/oldie
The text was updated successfully, but these errors were encountered: