Closed ntharim closed 9 years ago
An example:
@custom-selector :--buttons button, .button; :--buttons:matches(:hover, :active) { display: none; }
postcss-custom-selectors would generate:
postcss-custom-selectors
button:matches(:hover, :active), .button:matches(:hover, :active) { display: none; }
From this, postcss-selector-matches would generate:
postcss-selector-matches
button:hover, .button:hover, button:active, .button:hover, button:hover, .button:active, button:active, .button:active { display: none; }
Shouldn't the output be close to something like this instead?
button:hover, button:active, .button:hover, .button:active { display: none; }
This gets worse if you're trying to match at lot of things like :matches(:hover, :active, :focus, .active).
:matches(:hover, :active, :focus, .active)
Fix released as 1.1.1
An example:
postcss-custom-selectors
would generate:From this,
postcss-selector-matches
would generate:Shouldn't the output be close to something like this instead?
This gets worse if you're trying to match at lot of things like
:matches(:hover, :active, :focus, .active)
.