-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SyntaxError: '>input:-webkit-autofill' is not a valid selector #116
Comments
@alissalkvc
this is in effect an invalid selector and I believe any browser will treat it the same. Try removing the '>' at the beginning or add '*' in front of it to make it a valid selector. Try it in browsers and you will see they treat the selector as invalid. |
@dperini The fact is that we're not using it as a standalone selector. It's part of a If we have, for example |
@alissalkvc & @otaviomad |
@dperini (We're having this on our own components. I'm unsure whether this issue is also applicable to Material UI) |
@otaviomad @alissalkvc |
It’s not quite as easy as just pasting when the code snippet works with 2.2.7 - the failure only happens when Jest tests are run using versions after 2.2.7. usually, I don’t see anything because tests are all passing, but with this error (anything over 2.2.7) I suddenly get errors like these: ‘’’
I’m not sure what changed in 2.2.8 that would have caused this selector to suddenly cause test failures? |
Hi all, I'm using Material UI in my project, which has a few CSS rules with the pseudo-selector
:-webkit-autofill
.All was good until a subdependency updated from
v2.2.7
of this package. I started to get this error when running jest tests:Adding
"nwsapi": "2.2.7"
to my Yarn resolutions fixed the issue. I see the issue as soon as I start usingv2.2.8
, and still see the issue inv.2.2.10
. I assume this selector should still be allowed and valid? The only spot I see this selector mentioned is https://github.com/dperini/nwsapi/blame/45e88dee2b02276834bd53584fe82fe031c51592/src/nwsapi.js#L90thanks for all that you do and let me know if I can provide any additional information!
The text was updated successfully, but these errors were encountered: