:focus-within sometimes gives an invalid selector warning #51
Comments
alan-agius4
added a commit
to alan-agius4/critters
that referenced
this issue
Dec 14, 2020
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-classes Closes GoogleChromeLabs#51
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The pseudo-class
:focus-withinsometimes gives an invalid selector warning.For example, this code
.group:focus-within .group-focus\:block {...}produces:I doubt that any class with
:focus-withinwill ever be used in critical CSS, but those warnings create some noise. A workaround if to setlogLevelto "error".This issue probably causes #47.
On the other side, I am sure some simple selectors like
foo::focus-withinare accepted.The text was updated successfully, but these errors were encountered: