Roman Dvornov

An error is raised because csstree can't validate such values properly. It's unclear what you mean by 'skip any var(...)'. If you're suggesting discarding `var(...)` from a value, it would...

Thank you for the clarification. What you're describing is the same approach I mentioned in my comment. It's challenging to implement due to the way syntaxes are defined and how...

@romainmenke Thank you for bringing this up. Interesting. I'm not entirely sure how to address it at the moment, but I'll give it some thought.

"Paste from clipboard" button added on welcome page:

@bartveneman Yes, relaxed CSS nesting parsing is not supported yet, but it's a priority for implementation. Preparations have been made, but there are still some challenges to complete the implementation.

`` is used in `@font-palette-values/override-colors` However, `@font-palette-values/override-colors` was updated in the spec and now uses `` instead of ``. So, `@font-palette-values/override-colors` needs to be updated as well.

CSSTree and validator have no support for selector validation yet. The `@media` example is valid, since `gsdfgdfg` is matching as `media-type` and it defined as ``, so it can be...

CSSTree currently skips validation of declaration values that contain `var(...)`, but it would be beneficial to at least validate the variable names. It would be great if you could create...

@nzakas The limit exists to catch suboptimal matching and prevent infinite loops. The first example is relatively short and is more likely to fall into an infinite loop. The second...

Matching implemented in [lib/lexer/match.js](https://github.com/csstree/csstree/blob/master/lib/lexer/match.js) It uses a match graph which is building from a definition syntax tree in [lib/lexer/match-graph.js](https://github.com/csstree/csstree/blob/master/lib/lexer/match-graph.js) Needed to debug the matching process for a problematic value. The...