How should we handle "level"/stability of features?

[MoOx]

http://babeljs.io/docs/usage/experimental/

Reference: http://www.w3.org/Style/CSS/current-work#legend

Stage 0 - Unofficial draft (that's where it's interesting for users)
Stage 1 - working draft
Stage 2 - last call before candidate recommendation
Stage 3 - candidate recommendation
Stage 4 - proposed recommendation
Stage 5 - recommendation

It's a lot. Maybe too much ?

[MoOx]

Also that might helps for some possible features postcss/postcss#140

[magsout]

it's interesting and I like the idea.

It's a lot. Maybe too much ?

it is the standard w3c...

[magsout]

List of some css4 selectors http://css4.rocks/css4-selectors/

[MoOx]

Hum not sure what you mean. cssnext is about the syntax and might not handle a lot of new selector (except :matches maybe).

[MoOx]

oups

[magsout]

it's just to give plugin ideas that can be created

[magsout]

#106 and #17

[MoOx]

yes sure. And #80

[jonathanKingston]

Certainly #80 would be something that is most important to be excluded due to it being 0.

I think this makes more sense than turning off individual filters so no seems complete sense and not too much.

[Macxim]

It's an interesting idea. I don't think it's too much at all. As @magsout pointed, it matches the W3C specs which is consistent with the main purpose of the entire project.

[MoOx]

I just took a second look and found this:

• last call are just considered as WD: "Document maturity level: Working Draft."
• I didn't see a lot of "proposed recommendation" on this page http://www.w3.org/TR/tr-groups-all#tr_Cascading_Style_Sheets__CSS__Working_Group

So what about this:

Stage 0 - Strawman
Stage 1 - Unofficial draft
Stage 2 - Working draft
Stage 3 - Candidate recommendation
Stage 4 - Recommendation

Default to 2

Just a rip of babel stages :)

[magsout]

👍

[kaelig]

Seems like a great idea. 👍

[MoOx]

This way to handle the "issue" seems compromised. See how babel will evolve babel/babel#2168.
I opened a discussion on PostCSS repo to discuss about some things I could bring back to its core postcss/postcss#477

I need to think about how cssnext can evolve to follow this changes. Maybe it should die and provide an .postcssrc has a replacement in a near future.

[kevinSuttle]

https://developer.mozilla.org/en-US/Add-ons/SDK/Guides/SDK_API_Lifecycle#Stability_Index maybe?

[jescalan]

👍 agreed with not including lower than level 2. The last thing we want is to ship out a feature only to have people rely on it then have it pulled later.

[MoOx]

@jonathantneal feel free to share update about your work on css-db here. I guess cssnext can become: preset-stage-0 (or 1?) or just include all stage and allow people to choose stage. Thoughts?

[danny-andrews]

I guess cssnext can become: preset-stage-0 (or 1?) or just include all stage and allow people to choose stage. Thoughts?

@MoOx I like the idea of allowing people to choose the stage they want, but we can avoid including all stages by splitting this repo into a monorepo which has packages for each stage, similar to how babel does it. That way, you could just install postcss-preset-stage-2 and only have to download the stage-2 transforms.

p.s. I don't have much context on this yet, so excuse my ignorance, just wanted to jump in the conversation and see if I can help in any way. I'm really excited to be able to use future css features via postcss with the ease and flexibility I use future js features via babel!

[MoOx]

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