You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 25, 2024. It is now read-only.
The pseudo-class :focus-within sometimes gives an invalid selector warning.
For example, this code .group:focus-within .group-focus\:block {...} produces:
.group:focus-within .group-focus\ -> '.group:focus-within .group-focus\' is not a valid selector
I doubt that any class with :focus-within will ever be used in critical CSS, but those warnings create some noise. A workaround if to set logLevel to "error".
At the moment critters doesn't correctly handle pseudo-class in the middle of the selector string and pseudo-class which take a value such as `:not`
Example
```
.mat-slider:hover .mat-slider-track-background
.mat-slider-min-value:not(.mat-slider-thumb-label-showing):hover.mat-slider-disabled .mat-slider-thumb
```
More context about CSS pseudo-classes can be found https://developer.mozilla.org/en-US/docs/Web/CSS/Pseudo-classesClosesGoogleChromeLabs#51
The pseudo-class
:focus-within
sometimes gives an invalid selector warning.For example, this code
.group:focus-within .group-focus\:block {...}
produces:I doubt that any class with
:focus-within
will ever be used in critical CSS, but those warnings create some noise. A workaround if to setlogLevel
to "error".This issue probably causes #47.
On the other side, I am sure some simple selectors like
foo::focus-within
are accepted.The text was updated successfully, but these errors were encountered: