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
Sass challenges don't work #12699
Comments
@Azbo400 Thank you for reporting this issue. It looks like we don't actually support compiling the Sass yet 😅 |
@systimotic Oh haha, that makes sense! Thank you 😄 |
Oh sorry! We should have given folks a head's up that this section wouldn't work properly. Thanks for the issue, @Azbo400 |
@HKuz That's fine, no problem. 😃 |
Yeah. Its not working. Will there be any notification when it is fixed? |
We don't support the "saas" yet! Lmao!!!
On Jan 22, 2017 12:19 AM, "Pramod Potdar" <notifications@github.com> wrote:
Yeah. Its not working. Will there be any notification when it is fixed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#12699 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVHZeUIbLrZVFpBbIy0z9uTcDlOwHHoDks5rUvULgaJpZM4LqJWk>
.
|
They don't want any sass from you. Jokes |
I agree that it'd be a good idea to warn people that Sass doesn't work yet. In the meanwhile, I recommend folks follow the Sass official page's guide to installing a Sass compiler and following their guide (and / or FCC's Sass tutorials) on their own machines. The guide starts here: http://sass-lang.com/install |
No agreed, there's more to it than white space. What I did notice is that - with the @while example - if I keep pressing the "Run the Tests" button then - if there are no actual errors - after 4-5 presses, it works, whereas if there is a genuine error it never passes. Not exactly ideal behaviour but would suggest a low-level error rather than one linked to an actual syntactic error in the code being submitted by the user. |
Hi all, whatever the issues are, they appear to be fix. Passed the challenge first time & i'm using Chrome Version 67.0.3396.87 (Official Build) (64-bit) |
Nope, still happening to me when I try the tests. Seem to only affect some users. |
Ran into the same issue-- FireFox 56.0.2. ===== |
@mahmoud-coo6 Does your method work on Apply a Style Until a Condition is Met with @while? |
I fix Apply a Style Until a Condition is Met with @while? Challenge by using Firefox instead of google-chrome it's worked for me. |
i had add background style to the div tags..... to get these bugged sass challenges to pass their test....!!
|
here the solution @flyfishingbarbara : there some time not worked because there is bug in website <style type='text/sass'> @each $color in blue,black, red { .#{$color}-bg { background-color: $color;} } div { height: 200px; width: 200px; } </style> |
It wouldn't work on Chrome 68.0.3440.106 and not on Opera 55.0 but it worked flawlessly on Firefox 59.0.2 (all 64-bit). Last three exercises did need a bit of "Run the Test" button spaming though |
@raisedadead @ValeraS |
@paulywill This is not related to this issue, and the issue has already been solved in the master branch. |
lol, I met the same problem... |
On Firefox Developer Edition (72.0b2 (64-bit)) it does not work. |
@nmichalakis What errors are you seeing in the browser console? |
@RandellDawson i found the "bug" if there is a space between the variable name and the ":" it does not compile correctly. Is this something that happens on plain .scss files too? |
Please open a fresh issue with these details. Thanks. |
SASS use-each-to-map-over-items-in-a-list beta challenge impossible@each $color in blue, black, red { |
Challenge storing-data-with-sass-variables has an issue.
User Agent is:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
.Hello Everyone, I think I found a bug in the challenge Storing Data With Sass Variables. I think I did everything right, but the h2 and the .blog-post elements colour doesn't change to red. I pass two of the user stories but not these:
Your .blog-post element should have a color of red.
Your h2 elements should have a color of red.
It also doesn't change red. But it passes the user stories:
Your code should have a Sass variable declared for $text-color with a value of red.
Your code should use the $text-color variable to change the color for the .blog-post and h2 items
Thank you in advance, and the new things in Beta seem amazing keep up the great work! Can't wait to work through more of them! 👍
The text was updated successfully, but these errors were encountered: