Skip to content
This repository was archived by the owner on Dec 19, 2024. It is now read-only.

Remove some not future css plugins from next major release #375

Closed
Semigradsky opened this issue May 7, 2017 · 11 comments
Closed

Remove some not future css plugins from next major release #375

Semigradsky opened this issue May 7, 2017 · 11 comments

Comments

@Semigradsky
Copy link
Collaborator

  1. postcss-color-rgba-fallback
    rgba(153, 221, 153, 0.8) -> #99DD99
    http://caniuse.com/#feat=css3-colors (IE 8-)

  2. postcss-pseudoelements
    :before {} -> ::before {}
    http://caniuse.com/#feat=css-gencontent (IE 8-)

  3. pixrem
    2.5rem -> 80px
    http://caniuse.com/#feat=rem (IE 10-)

Good plugin pack for this plugins: https://github.com/jonathantneal/oldie

@MoOx
Copy link
Owner

MoOx commented May 9, 2017

Why not. Curious to know what people want.

https://twitter.com/cssnext/status/861801417719382016

@jonathantneal
Copy link
Collaborator

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.

@jonathantneal
Copy link
Collaborator

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:

Firefox support SVG filters (and CSS shorthand since FF35)

Confirmed by caniuse.

@Semigradsky
Copy link
Collaborator Author

Firefox has supported gradients since early 2015 in version 35 (we are on 53).

How about IE 11 support?

@timkelty
Copy link

The future of @apply is also not looking so good: http://www.xanthir.com/b4o00
I'd consider removing postcss-apply.

@jonathantneal
Copy link
Collaborator

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.

@jonathantneal
Copy link
Collaborator

How about IE 11 support?

IE does not support SVGs filters.

@Jessidhia
Copy link

I'd also suggest removing color from postcss-cssnext. Supporting the current css-color-function plugin not only (incorrectly) implements a spec that is considered dead by its author, but also prevents adding support for a possible real transform for the actual color function.

See comments by tabatkins on ianstormtaylor/css-color-function#35.

@jonathantneal
Copy link
Collaborator

If the name is locked to color-mod so that it matches the current spec, then I don’t see a problem in keeping it around.

@jonathantneal
Copy link
Collaborator

Possibly resolved by #445

@MoOx
Copy link
Owner

MoOx commented May 29, 2018

postcss-cssnext has been deprecated in favor of postcss-preset-env. Read more at https://moox.io/blog/deprecating-cssnext/

@MoOx MoOx closed this as completed May 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants