Open DavidHenri008 opened 6 years ago
@DavidHenri008 What version of postcss-selector-parser did this occur with?
@chriseppstein I cannot recall. I understand that my original post lack details in order to reproduce it. Honestly I do not remember the exact environment/project in which I saw this behavior. If you cannot reproduce it on your side you may consider this issue closed.
/cc @jonathantneal what do you think about this? postcss interpreted --foo: {}
as rule so we have selector, i think we should interpreted this as non standard tag
selector instead throw error
I am using postcss-preset-env which use this plugin and I am getting a parsing error when I have a "complex" custom property.
When a css file hat the following code:
I am getting this error: