Skip to content
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

3.3.3 regression with &:not(...) #1901

Closed
asottile opened this issue Jan 30, 2016 · 8 comments
Closed

3.3.3 regression with &:not(...) #1901

asottile opened this issue Jan 30, 2016 · 8 comments

Comments

@asottile
Copy link
Member

Input:

a, b {
    &:not(c) {
        d: e;
    }
}

libsass 3.3.2

a:not(c), b:not(c) {
  d: e; }

libsass 3.3.3

a:not(c, c), b:not(c, c) {
  d: e; }

ruby-sass 3.4.20: https://gist.github.com/asottile/262b30c2d4e41b88dfd2

@asottile
Copy link
Member Author

bisect tells me this is the first commit showing this behaviour: 964613e @mgreter

@xzyfer
Copy link
Contributor

xzyfer commented Feb 1, 2016

Thanks for the report @asottile. This will be addressed in 3.3.4.

@asottile
Copy link
Member Author

asottile commented Feb 1, 2016

Sounds great, I added a spec for it here: sass/sass-spec#724

@mgreter mgreter self-assigned this Feb 23, 2016
xzyfer added a commit to xzyfer/sass-spec that referenced this issue Mar 17, 2016
xzyfer pushed a commit to xzyfer/libsass that referenced this issue Mar 17, 2016
xzyfer pushed a commit to xzyfer/libsass that referenced this issue Mar 17, 2016
xzyfer added a commit to xzyfer/sass-spec that referenced this issue Mar 17, 2016
xzyfer added a commit to xzyfer/sass-spec that referenced this issue Mar 17, 2016
@joelperry93
Copy link

I am still getting this issue.
libsass 3.3.6
node-sass 3.7.0

Can't see this ticket referenced in the release notes. Did this get fixed?

Cheers

@xzyfer
Copy link
Contributor

xzyfer commented May 4, 2016

This was fixed in 3.3.4. The output in 3.3.6 matches Ruby Sass.

a:not(c), b:not(c) {
  d: e; }

@joelperry93
Copy link

Here is my SASS and the output. Is this the same issue as this ticket describes? I am getting it on libsass 3.3.3+

SASS
[class*="button-"] { &:hover:not(.button-disabled) { transform: translate(0, 1px); } }

Invalid CSS (libsass >=3.3.3)
[class*="button-"]:hover:not(.button-disabled):not(.tablesorter-pager .button.disabled) { -webkit-transform: translate(0, 1px); transform: translate(0, 1px); }

Valid CSS (libsass <=3.3.2)
[class*="button-"]:hover:not(.button-disabled) { -webkit-transform: translate(0, 1px); transform: translate(0, 1px); }

@xzyfer
Copy link
Contributor

xzyfer commented May 4, 2016

Where is .tablesorter-pager defined. Looks like you have an extend you're
not showing. The easiest way to know if there is a bug is to compare the
LibSass output to Ruby Sass 3.4.* on sassmeister.com.
On 5 May 2016 12:10 AM, "Joel Perry" [email protected] wrote:

Here is my SASS and the output. Is this the same issue as this ticket
describes? I am getting it on libsass 3.3.3+

SASS
[class*="button-"] {
&:hover:not(.button-disabled) {
transform: translate(0, 1px);
}
}

Invalid CSS (libsass >=3.3.3)
[class*="button-"]:hover:not(.button-disabled):not(.tablesorter-pager
.button.disabled) {
-webkit-transform: translate(0, 1px);
transform: translate(0, 1px);
}

Valid CSS (libsass <=3.3.2)
[class*="button-"]:hover:not(.button-disabled) {
-webkit-transform: translate(0, 1px);
transform: translate(0, 1px);
}


You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#1901 (comment)

@joelperry93
Copy link

Thanks for the response. It did turn out to be an issue with that .tablesorter-pager definition in another file. The 3.3.3 update must have started compiling it correctly and causing the issue on our end. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants