Nested @media rules render different from Ruby SASS

[mgreter]

Hi everybody

Nested @media rules are not rendered the same as with Ruby SASS.

Source SCSS File:

@media only screen and (max-width : 100px) {
    .outer { width: 10px; }
    @media only screen and (max-width : 200px) {
        .inner { width: 20px; }
    }
}

Libsass output:

@media only screen and (max-width: 100px) {
  .outer {
    width: 10px; }
  @media only screen and (max-width: 200px) {
    .inner {
      width: 20px; } } }

Ruby SASS output:

@media only screen and (max-width: 100px) {
  .outer {
    width: 10px; } }
@media only screen and (max-width: 100px) and (max-width: 200px) {
  .inner {
    width: 20px; } }

Although libsass output is valid css3, it's not valid css2.1.
For some more info see: http://stackoverflow.com/a/11747166

Thanks and have a nice day!

[akhleung]

Hmm, looks like Sass does some boolean algebra on nested media queries ... thanks for the report!

[lunelson]

Also with nesting retina media queries inside a width query. This Sassmeister gist illustrates it: if you switch compilers in the control panel you can see how ruby-sass 3.3 combines them correctly but libsass simply writes it out nested:

http://sassmeister.com/gist/8914969

[timbz]

the ruby code should be in Query::merge()
https://github.com/nex3/sass/blob/stable/lib/sass/media.rb

[JeroenVdb]

Does someone have a (temporarily) workaround for this problem?

[DedRain]

Hi all, any progress with this?

[HamptonMakes]

I'm going to open a new issue on this, since the second one seems like a different issue.

[HamptonMakes]

Oh shit, totally misread this. Sorry, I thought that was a merge against the original issue above. Sorry, missed that it's never been addressed at all.

[xzyfer]

I've started looking into this. It's one of the few major blockers IMHO.

[xzyfer]

This fixed via #800 and will be in 3.2.

[msikma]

I'm very glad this will be fixed with 3.2, this will make it easy to do e.g. retina-specific code inside code blocks for specific responsive sizes. Hoping the next release is finalized soon, any guesses as to when it'll be ready?

[xzyfer]

@msikma it's hard to say at the moment. You can #812 to keep up to date on the 3.2 release.