named colours behave oddly when used in variables

[blowback]

There's something odd going on with named colours. They're meant to be "indistinguishable from unqoted strings".

@function is_gold($c) {
    @if ($c == gold) {
        @return 'yes';
    }
    @return 'no';
}

div {
    foo: is_gold(gold);
    bar: is_gold(white);
}

sass gives me:

div {
  foo: "yes";
  bar: "no"; }

sassc gives me:

div {
  foo: 'no';
  bar: 'no'; }

[blowback]

simpler:

$gold: gold;
$white: white;

div {
    foo: if($white == gold, 'yes', 'no');
    bar: if($gold == gold, 'yes', 'no');
}

gives no/no not no/yes

[cahamilton]

I've noticed something similar with mixins converting over to LibSass.

Example:

@mixin button($button-color: null) {

    @if $button-color == red {
        background-color: #ff0000;
    } @else if $button-color == blue {
        background-color: #0000ff;
    } @else if $button-color == green {
        background-color: #00FF00
    } @else {
        background-color: #ccc;
    }

}

.btn-red {
    @include button($button-color: red);
}

.btn-blue {
    @include button($button-color: blue);
}

.btn-green {
    @include button($button-color: green);
}

.btn {
    @include button;
}

RubySass compiles as:

.btn-red {
    background-color: #ff0000; }
.btn-blue {
    background-color: #0000ff; }
.btn-green {
    background-color: #00ff00; }
.btn {
    background-color: #ccc; }

LibSass compiles as:

.btn-red {
    background-color: #ccc; }
.btn-blue {
    background-color: #ccc; }
.btn-green {
    background-color: #ccc; }
.btn {
    background-color: #ccc; }

[mgreter]

This seems to be fixed by latest master? @xzyfer maybe you can check?

[xzyfer]

I can confirm the latest master returns the following output

.btn-red {
  background-color: #ff0000; }

.btn-blue {
  background-color: #0000ff; }

.btn-green {
  background-color: #00FF00; }

.btn {
  background-color: #ccc; }

[xzyfer]

It's worth noting #00FF00 isn't normalised to #00ff00 but that's its own issue IMO.