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 Dec 28, 2021. It is now read-only.
4.1.0 seems to solve most issues, but now something else doesn't work. Unsure if according with spec. It worked prior v3 though.
The following does not compile at all. Using postcss-selector-matches to unfold matches in the example; does not affect the postcss-nesting processing as & + & is expected to work.
& + & is not invalid but meaningless according to the author (#17 (comment)). The idea is that & is not a selector but the element itself.
This opens to a case where
ol {
@nest&.li+&.li {
margin-top:5px;
}
}
should be valid as well as meaningful according to the spec. But as the author said (#17 (comment)), it is relatively rare and polyfilling this would need greater even expensive efforts, so we simply reject multiple & occurence in a complex selector.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4.1.0 seems to solve most issues, but now something else doesn't work. Unsure if according with spec. It worked prior v3 though.
The following does not compile at all. Using
postcss-selector-matches
to unfoldmatches
in the example; does not affect thepostcss-nesting
processing as& + &
is expected to work.Expected
The text was updated successfully, but these errors were encountered: