-
Notifications
You must be signed in to change notification settings - Fork 333
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
CSS-grid not supported. #395
Comments
sass 3.5 is already supported by this gem https://github.com/rails/sass-rails/blob/v5.0.6/sass-rails.gemspec#L17, so why it is not supported? |
It works perfectly well in development mode. It fails only in production environment with rake asset:precompile (aka heroku deploy). |
If it works in development and not in production with the same set of gems I recommend you to report the issue to your production environment since it seems to be related with it. sass-rails supports sass 3.5 and if it is fixed in sass 3.5 so you should be able to get it installed. If the issue is not fixed in sass 3.5, you should report the issue in the sass repository since sass-rails is just a wrapper around sass. |
I have the error locally when I run:
So, the problem starts here (locally) when I test my local environment in production mode. |
Can you please provide a sample application that reproduces the error? |
@rafaelfranca, I'm having a similar error using Just try:
It works on development, but not in production. The version of sass-rails is 5.0.6. |
sass-rails doesn't defines the sass behavior, the gem responsible for this is sass, if it is working in development and not production either it is a problem in sass or the production envrionment. |
Sass added support sass/sass#2233 |
See: sass/sass#2233
Summary: With the release of FF52 and GC57, CSS-grid layout is now supported. With this new feature, construct like
grid-template-columns: repeat(5, 1fr)
are present.The CSS function 'repeat' is not really supported by SASS.
Solution: The last version of SASS (3.5) addresses the issue.
The text was updated successfully, but these errors were encountered: