Interpolation #{$x}00ms gobbles one 0?

[asottile]

Bit by this after upgrading libsass (3.3.7 -> 3.4), though it appears they've simply made the behaviour there the same as sass. Unclear if this is a bug or if it is intended, it certainly seems strange:

Input scss

$x: 1;
a {
  b: #{$x}00ms;
}

Output css

a {
  b: 10ms;
}

Expected

a {
  b: 100ms;
}

Workaround

obviously this scss is slightly silly, this is a working version:

$x: 1;
a {
  b: #{$x}#{'00ms'};
}

or the actually sane solution:

$x: 1;
a {
  b: $x * 100ms;
}

[asottile]

I imagine what is happening is it is parsing 00ms as 0ms which makes sense, the interpolation is probably a red herring.

Either way, I'm happy to close this as wontfix, just surprised me :)

[nex3]

This works as expected on master; the old behavior you're seeing is due to our old weird interpolation semantics.

[asottile]

for what it's worth, the linked article is interesting but doesn't seem to explain this specific case. That said, I'm fine to accept that this is just a weird case that is probably poorly written code that needs refactoring :) It could also be that it was depending on a bug in libsass and only when libsass was made compliant with ruby sass did it expose this strange situation.