stylelint: CSS custom property set regression in selector-* rules - "cannot parse selector"

Describe the issue. Is it a bug or a feature request (new rule, new option, etc.)?

A bug related to parsing of custom property sets like this appeared in 7.11.0.

Which rule, if any, is this issue related to?

I’m not able to identify, sorry.

What CSS is needed to reproduce this issue?

body {

  --dot: {
    overflow: hidden;
    white-space: nowrap;
    text-overflow: ellipsis;
  };
}

What stylelint configuration is needed to reproduce this issue?

{
  "extends": [ "stylelint-config-standard" ]
}

Which version of stylelint are you using?

7.11.0

How are you running stylelint: CLI, PostCSS plugin, Node API?

npm script. See Glitch App (press Logs button above the files list).

Does your issue relate to non-standard syntax (e.g. SCSS, nesting, etc.)?

Yes, related to CSS mixins which are not yet standardized and abandoned by Tab Atkins.

What did you expect to happen?

No warnings to be flagged.

What actually happened (e.g. what warnings or errors you are getting)?

The code above caused following output (not error):

 7:3     Cannot parse selector

PS: no such warnings with 7.10.1

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 3
  • Comments: 15 (13 by maintainers)

Commits related to this issue

Most upvoted comments

@jeddy3 i think be best just add isCustom* utils now, because postcss v6 handle them to another way.