Packages: [CSS] Nested comments break highlighting

[deathaxe]

Adding a /* ... */ within an existing comment, results in the final */ not being matched anymore.

[rwols]

I'm not too familiar with CSS, but isn't it supposed to work like this? You end the comment block at the first */, and then the one after that is just considered a stray end-of-comment-block token. Do browsers render this correctly?

[rwols]

Comments may not be nested.

[deathaxe]

Understand. So it is an illegal.invalid instead?

Did not see any parse errors or something like that, so I expected it to be a valid construct. Not that I intend to use something like that normally. It was just the result of some investigations.

[rwols]

So it is an illegal.invalid instead?

Well, ideally yes, but the current syntax def doesn't account for that it seems.

[wbond]

I'm hesitant to add too many invalid scopes. We've been bitten by a number of false positives in the past. I'd rather rely on a linter than have false-positives.

[deathaxe]

I honestly was not aware of CSS not supporting such constructs by the specs. Just was wondering why it was not highlighted. As @rwols correctly pointed on the specs, this is not a real issue.