-
Notifications
You must be signed in to change notification settings - Fork 30
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
Deprecate or replace with postcss-color-mod-function #52
Comments
Any update on this? |
I never know if the lack of response means a lack of interest, or that any other interested parties are just busy, or if I just did a bad job explaining the issue. |
@jonathantneal I can understand your issue, and share the interest in the response. |
I'm a confused, why would this plugin be deprecated in favor of a deprecated concept? In any case, I like this plugin and would like to help maintain it, especially to solve #49. |
I do not want the color-mod to disappear |
@jonathantneal Are you still looking for somebody to take over supporting this project? If so, I'd be happy to dig in. I'm about to fork it to see if I can either figure out why an issue is happening or fix it if I have found a bug. |
This is great news. If we can get some smaller PRs, I will review and hand out maintainer status that way. Then after I can review a few npm publishes, I can hand over access there, too. I hope you don’t mind the gated philosophy; we’ve seen what happens we hand out access too easily and all the sudden bitcoin miners are distributed across npm. |
A smaller PR was brought in and released as 4.1.0. |
@jonathantneal I don't really understand the readme. Are both color() and color-mod() deprecated? |
I'm also curious about this. Is the CSS Color Module Level 4 spec introducing a different syntax or tool to solve the same problem? Or has the concept of color manipulation in CSS been removed from the spec completely? |
Appearently it has been removed here: w3c/csswg-drafts@034b063 The commit message states:
So, it's going to be added again, but most likely in a way that will cause a breaking change in the |
It will have a different syntax, yes (coincidentally we are discussing that syntax at today's CSS Working Group meeting) |
@EasterPeanut, it’s complicated, but yes, both the First, the CSS function named This is why the README says “ Second, the function named But this is why the README says “ @Paul-Hebert, by removing the Now, since my original request, I have received 2 maintenance PRs and neither contributor stuck around. I’ll talk with other PostCSS team members to see what we should do with this repo. |
Cool, thanks for the additional info, @grebaldi , @svgeesus , @jonathantneal ! |
In case anyone is interested, minutes of the 5 June CSS WG meeting on color modification functions |
Are there any developers interested in continuing this project, or should we deprecate it in favor of https://www.npmjs.com/package/postcss-color-mod-function ?
Note that, regardless of the name, the entire
color-mod()
function concept is deprecated.The text was updated successfully, but these errors were encountered: