Roman Dvornov

That’s not so simple. To rely on ``, we first need to implement it, since this token type is currently missing. It was removed from the spec many years ago...

Hm... probably renaming `urange` into `unicode-range-token` in `lib/lexer/generic.js` would be enough. It will be a bit confusing, but overall within the spec as it behaves.

Please remove the `^` from the `mdn/data` version. `mdn/data` can occasionally introduce breaking changes, so we need to pin it to a specific version to ensure stability. Additionally, run the...

My apologies – I mistakenly chose the wrong option, which caused all commits to be squashed into a single merge commit. Sorry about that.

My bad, false alert, everything fine :)

@romainmenke This isn't an issue with syntax definition or matching; it's a parsing error (`parse(...)`). Symbols like `%` and `|` are currently not allowed in values due to legacy behavior....

Based on the provided details it's hard to reproduce the issue. It might be related to Yandex Browser or be a specific to the document. Having a JSON document would...

The issue is caused by a missed extension for an import path. Regression was added in last version, so you should try previous version for now. The issue will be...

The issue should be resolved now. Please, try with new version [v1.0.0-beta.84](https://github.com/discoveryjs/discovery/releases/tag/v1.0.0-beta.84)

CSSTree matches the value on IE legacy syntax. You can try it here: https://csstree.github.io/docs/syntax/#Property:filter I'm going to remove IE legacy syntax from `` since it non actual anymore. This should...