-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
nested element type selector broken #274
Comments
Testing it on the https://stylis.js.org/ it seems like it works as expected. This might be an issue with Emotion - could you create a full runnable repro case of the problem? |
added runnable examples in the issue raised at emotion ☝️ |
Thank you! As to the correct output - remember that on the Stylis docs page everything is implicitly wrapped in [namespace] .button {
color: blue;
}
[namespace] .button:hover:enabled,
[namespace] .button:focus:enabled,
[namespace] .button.is-active:enabled,
a[namespace] .button:hover,
a[namespace] .button:focus,
a[namespace] .button.is-active {
color: red;
} I've tried comparing with Sass but it turns out that this is not even a valid Sass because I get this error:
If I just remove the [namespace] {
color: blue;
}
[namespace]:hover:enabled,
[namespace]:focus:enabled,
[namespace].is-active:enabled,
a[namespace]:hover,
a[namespace]:focus,
a[namespace].is-active {
color: red;
} then this looks exactly the same as your expected output. Could you confirm that? Maybe I'm missing something here. |
Hey @Andarist, thanks for looking into it and you're right the following looks like correct. It seems to be a change in emotion which caused my issue then 🤔 |
Thank you for confirming! Gonna close this issue here then - let's continue looking into it in the issue created for Emotion. |
thanks @Andarist for your work! |
I'm upgrading from emotion 10 to 11 (which bumped stylis up) and experiencing some changes in how my "button" selector works which I apply to
button
anda
elements.This previously generated the following css
but appends the "tag" selector wrongly
The text was updated successfully, but these errors were encountered: