Discrepancies between libsass parsing and the ruby gem #58

Closed
gregtillbrook opened this Issue Nov 6, 2012 · 2 comments

Comments

Projects
None yet
3 participants

Hi there, there seems to be some differences between libsass and the ruby gem regarding string handling.

e.g.
For desired css of the form;

background: url(/static_loc/img/beta.png);

I was able to write the following scss;

$base_url: "/static_loc/";
background-image: "url("#{$base_url}"img/beta.png)";

However, when I switched to the ruby gem (due to other issues) I had to omit several quotes to get the same css;

$base_url: "/static_loc/";
background-image: url(#{$base_url}img/beta.png);

Not a massive issue (I can probably refactor it so it works for both) but I thought it'd help to raise an issue as I assume you folks want to keep all sass parsers in sync?

Cheers,
Greg

akhleung commented Nov 6, 2012

Thanks for the heads-up -- we expect that there will be edge cases like this. I'll try to iron them all out as development continues, but right now they're a low priority compared to getting other major features in!

Okay, this one should finally be fixed, but there are other similar discrepancies involving concatenation of adjacent strings and expressions (and I think official Sass has some bugs in this area too).

@akhleung akhleung closed this Jul 2, 2013

anlutro pushed a commit to alprs/libsass that referenced this issue Feb 2, 2015

Merge pull request #58 from lunelson/master
Tests for nested maps, map-remove, multi-assign...

mgreter added a commit to mgreter/sass-spec that referenced this issue Apr 22, 2016

@mgreter mgreter referenced this issue in sass/sass-spec Apr 22, 2016

Merged

Add todo spec test for libsass issue 58 #803

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment