-
Notifications
You must be signed in to change notification settings - Fork 822
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
Improve CSS Support #3642
Improve CSS Support #3642
Conversation
The semicolon is optional reading the examples. This change implements: semicolons are required after property declarations, but not after margin declarations.
293093d
to
7639dc8
Compare
I intent to merge this next weekend. If you want to object, feel free to do so. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks sane. Good to see we're generating files from grammars. Just a little comment: we may want to regenerate files from grammars before compiling (in case one forgets to regenerate them by hand).
Hi, I have a very naive question. I only see that for css we use antlr 3.x and the current antlr is 4.x. I'm not aware how many grammar we have in codebase. But would it be an idea to migrate to last ? |
Without a good argument I think it would be no benefit. Rewriting the grammar just poses chances to break the code. |
@ebarboni @matthiasblaesing AFAIK Antlr4 exposes the AST through the visitor pattern (or through events), i.e., you don't have it in memory. The migration Antlr3 to Antlr4 is not straightforward. You'll have to build the AST yourself (see, https://stackoverflow.com/questions/29971097/how-to-create-ast-with-antlr4 for instance). |
Introduce partitial support for CSS Selector Level 4 (:not, :where, :is)
Before:
After:
Improve parsing of the contents of @page declarations
Before:
After: