-
Notifications
You must be signed in to change notification settings - Fork 465
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrectly output integers as float is precision is 0 #1153
Comments
Once again, the logix seems to be more complicated then anticipated and again not sure if wanted behavior or just a ruby sass bug? //cc @xzyfer input.css foo {
bar: (0);
bar: (.0);
bar: (0.0);
bar: (-0);
bar: (-.0);
bar: (-0.0);
bar: (42);
bar: (-42);
bar: (43.0);
bar: (-43.0);
bar: (44.0000);
bar: (-44.0000);
bar: (45.00001);
bar: (-45.00001);
bar: (42.84);
bar: (-42.84);
bar: (42.24);
bar: (-42.24);
bar: (42.845555);
bar: (-42.845555);
bar: (42.245555);
bar: (-42.245555); } Ruby sass output: foo {
bar: 0;
bar: 0;
bar: 0;
bar: 0;
bar: 0;
bar: 0;
bar: 42;
bar: -42;
bar: 43;
bar: -43;
bar: 44;
bar: -44;
bar: 45.0;
bar: -45.0;
bar: 43.0;
bar: -43.0;
bar: 42.0;
bar: -42.0;
bar: 43.0;
bar: -43.0;
bar: 42.0;
bar: -42.0; } Seems to be a special case if the value was actually rounded. IMO we have a similar expection already in that function, so I might be able to implement it "correctly" ... |
Yes. When I recently refactored this code I applied to "special cases" always because it was semantically equivalent and the old behaviour wasn't. This issue specifically refers to making the special case only apply to rounded numbers. |
Originally reported in #1140 (comment)
Libsass with precision 0
Ruby Sass with precision 0
The text was updated successfully, but these errors were encountered: