[bug] @extend is not working properly & code color messed up

I'm using WebWorkbench 2.0.501.19486

I used to work with the Ruby compiler but this WebWorkbenchTool is way better and comfortable to use. However, my SCSS files seem to be compiled differently when using the @extend feature.

For example if I use:

.normalLink {
       color: black;
       text-decoration: underlined;

       &:visited {
          background-color: red;
       }
 }

.specialLink {
        @extend .normalLink;

        &:visited {
           border: solid 1px blue;
        }
 }

I expect it to be compiled into (which is OK if I use the Ruby compiler):

.normalLink, .specialLink {
  color: black;
  text-decoration: underlined;
}
.normalLink:visited, .specialLink:visited {
  background-color: red;
}
.specialLink:visited {
  border: solid 1px blue;
}

But the compiler on the WebWorkbench switches the order on the extended selector (:visited is placed first):

.normalLink, .specialLink {
  color: black;
  text-decoration: underlined; 
}
.normalLink:visited, :visited.specialLink {
  background-color: red;
}
.specialLink:visited {
  border: solid 1px blue; 
}

So I'm missing the red background property to apply on all selector that is extending the original selector.

The other (less important) bug is that code coloring is messed up right after variable interpolation:

// Variable interpolation
$mainTextFont: Arial;
$mainFontSize: 12px;
$mainLineHeight: 1.5em;

body
{
    font: #{$mainFontSize}/#{$mainLineHeight} $mainTextFont;
}

// Code here no longer is colored

That code works, but the code colors are lost right after that. Also after a Function

// Function to create a set of css classes
$i: 20;
@while $i <= 200
{
    .tbx#{$i} {
          width: $i + px;
    }

    $i: $i + 20;
}

// Code here no longer is colored

I think this tool is great and a MUST for every developer. A great feature would be to automatically detect partials (SCSS files starting with an underscore) and avoid compiling those into CSS. Curently I need to manually delete the CustomTool property on each SCSS to avoid compiling.

Another nice feature would be to allow the integration with some CSS frameworks mixins such as COMPASS, BluePrint or 960. Currently I need to copy all the framework's mixins files into the project.

I'm willing to pay for the 'Minify' SASS feature, but.. does it allow to choose one from all four compression options? (expanded, nested, compact and compressed)

Thanks so much for this tool... Love it!

Thanks for the feedback and the kind words! We'll take a look at that @extend behaviour -- we're actually just calling the Sass Ruby compiler ourselves so maybe this is just an issue with us using an old version of the compiler or some odd behaviour on IronRuby. We'll also look into the variable interpolation issue.

Thanks also for the feature suggestions. Some of these are on the radar but are going to require some architectural changes which we aren't able to resource right now, but hopefully in the next couple of months!

Regardining minification, the good news is that even in the free edition you can apply compression within the Sass compiler using the special directive format described in http://www.mindscapehq.com/forums/thread/4460. The Pro edition creates a separate minified file using the Yahoo library; this is particularly handy for debugging because you can have both an uncompressed .css file for testing and a .min.css file for production. (And of course Pro includes other features such as block comment/uncomment, automatic formatting and function signature help.)

Just download the latest version (3.2.200.20308) and tried to see if the @extend bug has already been fix, but apparently it is not.

I believe SASS @extend feature is one of the most valuable to have since it enables class inheritance in a neat way.

Are there any plans to include the fix for this?

We've just switched over the Sass compiler in the nightly builds and we believe the @extend bug is now fixed. Could you give the latest nightly a go and see if you still experience the problem? See the FAQ sticky thread for info about downloading and installing nightly builds.

I am having the same issue with the @extend bug.

Is the nightly available to free users, or only commercial users? I went in the store and looked at the downloads page, but don't see anything for Web Workbench?

Actually, nevermind...looks like there was an update to Web Workbench in Visual Studio that I didn't know was there, and the issue seems to be fixed.