Repository navigation
API to return whether a selector has non-standard syntax. #135
Description
- add a strict parse mode so that any non-standard syntax is an immediate error.
- When not strict, it should be possible to find which nodes contain non standard syntax and for complex nodes like Attribute, which part(s) are violating the css spec.
Reacted by Alexander Akait
Activity
alexander-akait commentedon Mar 30, 2018
@chriseppstein Also maybe we can support non standard comments
//?chriseppstein commentedon Mar 30, 2018
I'd rather postcss filter that out so that it's not part of the rule's selector value.
chriseppstein commentedon May 16, 2018
postcss/postcss#1149
TIL about
postcss-scss. I think the selector parser and tokenizer should be updated to have a syntax option and then the parser should non-standard syntax correctly or error out based on the current syntax setting. Right now it's all mashed together and unpredictable.MoOx commentedon Nov 8, 2026
Parked in #357, which collects the design issues that would need a major. This is not a rejection: if it blocks you, say so in #357 with a concrete use case and it can be taken back out.