You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, @jeddy3!
Can you move the issue to csstree issues?
In the meantime, let me answer here. In short, it's a bit complicated and therefore postponed for a while (it's good to have an issue still).
CSSTree supports things are supported by browsers first. As I know level 4 is not supported by any browser yet (correct me if I'm wrong). It may be an extension for default syntax still.
I read this module a while ago. While color() looks simple, I found a problem with color-mod syntax. In current form, it's unusual and requires improvements in lexer syntax matcher. Now it is not known exactly that the syntax will be the same in the future (it's a draft). So it's unclear should we do these improvements or not. Supporting for a part of the module looks odd. One more solution to rewrite a color-mod syntax in a regular way and then suggest those changes to the module. But this requires an unknown amount of time. That's why I decided to focus on more obvious things.
It's very exciting to watch so many of the
1.0
roadmap items get ticked-off!I was wondering if support for the CSS Color Module Level 4 (Editor's Draft) was under consideration, in particular, the
color()
function (playground here)?Currently the following CSS:
Produces the following warnings:
The text was updated successfully, but these errors were encountered: