Skip to content
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

Adjust globals for sass 3.2 compatibility #5632

Closed
wants to merge 1 commit into from
Closed

Adjust globals for sass 3.2 compatibility #5632

wants to merge 1 commit into from

Conversation

navneetgarg123
Copy link

Minor adjustments to global declarations so that Sass 3.2 doesn't throw deprecation errors/warnings when compiling to css.

@bfin
Copy link

bfin commented Aug 19, 2014

Second this. Throws deprecation warnings through (ruby) sass v3.3.14 and errors in v3.4.0.

Made these same changes locally and it's now working fine with v3.4.0.

@cmwinters
Copy link
Contributor

Unfortunately this breaks in Libsass. See sass/libsass#278

@cmwinters cmwinters closed this Aug 20, 2014
@noeljackson
Copy link
Contributor

It looks like it shouldn't be an issue anymore? sass/libsass#409

Am I wrong with this assumption?

@niallobrien
Copy link

Still fails for me.

smartperson added a commit to smartperson/foundation-rails that referenced this pull request Sep 15, 2014
This is tied to issues mentioned in:
http://foundation.zurb.com/forum/posts/18856-sass-342-compilation-proble
m
sass/sass#1397
foundation/foundation-sites#5636
foundation/foundation-sites#5632

Since it seems to be taking time for smarter minds to come up with
changes to Foundation 5 that will get it playing nice with sass 3.4,
let’s at least modify the dependencies in the meantime so more users
don’t update their gems and spend forever debugging a very unusual
issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants