CSS selectors compiled wrong

[krisdigital]

When updating to the newest Rails version 4.2.5.1, sassc (1.8.4) and sassc-rails (1.2.0) were also updated. Suddenly Bootstrap is compiled with strange errors. For example input-groups:

.input-group .form-control:not(:first-child, :first-child, :first-child):not(:last-child, :last-child, :last-child)

The :first-child and :last-child statements should obviously only appear once and let the statement break in Chrome and Firefox. Switching back to sass-rails solves the error.

Any idea what change caused this?

[bolandrm]

Try sassc-ruby 1.8.3. This may be a bug in the latest version of libsass.

[krisdigital]

@bolandrm Thank's for the suggestion. Just tried it and does not make a difference!

[dsteppeler]

Hi!
I am interested in a fix for this as well. Currently it is preventing me from using this gem.
It seems to be related to this one: sass/libsass#1901

Regards!

[samjewell]

I'd also love a fix for this.
We saw it around checkboxes and radio buttons

:not(:checked)

was compiled to

:not(:checked, :checked)

[bolandrm]

I've just released sassc 1.8.5 which upgrades libsass to 3.3.4. Please give that a try!

[ElManouche]

I've now sassc 1.9.0, but the same issue.
Any other suggestions?

[ElManouche]

I have more details after some tests.
The error only appears when the parent selector has a period as well:

.test {
  // this works
  .test__elem {
    &:not(.active) {
      opacity: 0.5;
    }
  }

  // this creates a bug in the 'not' selector
  .test__item,
  .test__item2 {
    &:not(.active) {
      opacity: 0.5;
    }
  }
}

is compiled to:

.test .test__elem:not(.active) {
  opacity: 0.5;
}

.test .test__item:not(.active, .active),
.test .test__item2:not(.active, .active) {
  opacity: 0.5;
}

[EDIT]: I opened a bug in libsass

[bolandrm]

@ElManouche could you please post this bug here: https://github.com/sass/libsass/issues and link your issue back to this thread so we can track it?

[xzyfer]

@bolandrm this is fixed in 3.3.4.

[bolandrm]

@xzyfer i thought so... sassc 1.8.5 / 1.9.0 are using libsass 3.3.4, so this should be fixed.