-
Notifications
You must be signed in to change notification settings - Fork 262
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
Faulty nesting detection with at-rules #214
Comments
@cheeaun thanks for the amazing and detailed bug report! You are correct the bug should be in Would you have time to further debug |
@giuseppeg I've also tried to replicate the bug on I suspect that when |
This happens because |
@thysultan yep that indeed fixes @cheeaun's issue. Mind taking a look at the PR #216 ? However there seem to be a bug in Stylis and media queries are prefixed span {}
@media (min-width: 480px) { div { color: red } }
/* @media[prefix](min-width[prefix]:480px[prefix]) div[prefix]{color:red} */ :hover {}
@media (min-width: 480px) { div { color: red } }
/* @media[prefix](min-width[prefix]:480px[prefix]) div[prefix]{color:red} */ :hover { color: green }
@media (min-width: 480px) { div { color: red } }
/* [prefix]:hover{color:green}@media[prefix](min-width[prefix]:480px[prefix]) div[prefix]{color:red} */ |
@giuseppeg Interesting, i see what could be the issue there. |
published |
Will also appear
|
@thysultan could it be a parsing issue? Or do you think that is our plugin's fault? |
@giuseppeg The latter, specifically related to #313 (review). |
@thysultan awesome thank you! |
I upgraded to the latest version of
styled-jsx
at1.0.1
and been getting this error:Did a little research, ran tests on both
styled-jsx
andstylis
, found that:This is the current test and it passes ✅
Added a faux
span
and this passes too ✅BUT...
Add a newline and this fails ❌
If the lines are flipped around, this passes ✅ 😅
I suspect this is relevant to the
disableNestingPlugin
method instyle-transform.js
and thecascade: false
option passed intostylis
. This applies to@keyframes
too.The text was updated successfully, but these errors were encountered: