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
Right now CSSTree returns Parse error: Identifier is expected error, while allowing either only declarations or only nested rules.
While this module is still in Editor's Draft, it is quite possible that other modules could allow this kind of syntax (and this could be helpful for external tools too of course).
The text was updated successfully, but these errors were encountered:
Thank you for issue!
Yep, just yesterday thought about the possibility of the rules within the block, and decided that it can be added to the parser, since there is a case in this module. Also this addition will allow to parse some non-standart (yet) things as side effect.
I'm going to implement it soon.
While it is really experimental now and there is chance it would go away/be changed, if adding support for this is not really complicated, then it would be nice to have.
Looks like issue is solved. Since alpha14 no parse errors. @page at-rule parses as expected. Custom properties value parses as balanced Raw.
Feel free to re-open issue or open new one if there are some other problems.
Some CSS modules have mixed rules and declarations inside at-rules. An example: Paged Media Module allowing stuff like this:
Right now CSSTree returns
Parse error: Identifier is expected
error, while allowing either only declarations or only nested rules.While this module is still in Editor's Draft, it is quite possible that other modules could allow this kind of syntax (and this could be helpful for external tools too of course).
The text was updated successfully, but these errors were encountered: