This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
The SASS parser seems to have some issues. I get syntax error warnings on some fairly standard CSS selectors such as: a:focus Actually it appears to choke on any pseudo class or nested selector. |
|
|
Thanks for reporting this. The next update (up within the next 24 hours) will cover top-level pseudoclasses and the direct child (>) operator, and we're reviewing whether we're missing any other CSS selectors. Nested selectors should be working already though. Could you provide us with a small sample that demonstrates the problem you're seeing please? Thanks! |
|
|
Sorry, by nested selectors, I meant child selectors. Haven't played around much with the nesting yet, since the first big issue I ran into when convering to SASS was the syntax error on my psuedo-classes. |
|
|
Okay, gotcha. Just to update you, the update for the top-level pseudo-classes and the child (>) combinator shipped today; we've since implemented the remaining combinators and support for some other selectors (specifically the * selector and attribute selectors) which should go up sometime in the next couple of days, but you will still see errors on those in the meantime. You can ignore these as spurious -- the Sass compiler will still process them correctly even though the highlighting falsely indicates an error. Thanks again for the feedback! |
|
|
More syntax errors with the new version: font-family: 'Arial Black', Sans-Serif; Removing the space in Arial Black gets rid of the syntax error, but it's perfectly valid CSS for font names with spaces. Not sure exactly what's wrong with either of these two, but they both generate syntax errors: background: url('Images/Background_Main.jpg') no-repeat center -100px; div.registration ol.form input[type=text], div.registration ol.form select
|
|
|
Thanks for the error reports and for your patience! The issue with spaces in font names will be fixed in the next build. The "background" was caused by a quirk where we couldn't handle url() if it was in the first position in a list; that too will be fixed in the next build. The selector list was erroring because we of a problem with commas after an attribute selector -- that should also be fixed in the next drop. Once again we appreciate you letting us know about these spurious errors and we hope we will soon have them all knocked on the head! |
|
|
Hello, i'm working with Sass too, and got one issue this afternoon with the :not() pseudo selector. Example :
ul li:not(:last-of-type) { margin-left: 2px; } Is reported as a syntax error by the editor but compiles fine. After encoutering this issue the colored syntax editor stops working for next lines.
|
|
|
Thanks for letting us know about this. There will be a fix in the next drop (should be up within 24-36 hours -- check the VS Extension Manager Updates tab). |
|
|
|
|
|
Maybe that's one way to write it, but the idea of the new style of SASS being syntactically valid CSS means that a:focus{} should work just as well, and should not generate any syntax errors. |
|
|
Yes, a:focus should work. We believe this was fixed early last week -- if anyone is still seeing problems with this then please check the Updates tab in Extension Manager (current build is 18072), and if you're still getting squigglies, do let us know! |
|
|
Hey! I have found two issues! I get syntax error warnings on a { background-image : url(../images/back_red.png); } and div { width : 100px; height : 100px } |
|
|
My guess is the background url doesn't have quotes and the colon in the second example is preceeded by a space. Neither of these should generate syntax errors though. |
|
|
We have a problem with unquoted URLs at the moment which we are looking into. In the meantime, quote the URL: url('../images/back_red.png') In your second fragment you are missing a semicolon after the height : 100px property. |
|
|
Great Tool! A couple other syntax errors: It seems like h1 > div works fine, but something:first-child is still giving me a syntax error. Another error is with the @include it seems to be fine when it is @include shadow(0,0,0, #FFFF) but if i use rgba with double () then I get a syntax error i.e. @include shadow(1,1, rgba(0,0,0,.5))
It also does not like this mixin, I think because of the rgba again -- or maybe I missed something. @mixin border_bevel($width: 1px, $hilight: .3, $shadow: .3) { border: solid 1px #000; border-color: rgba(255,255,255, $hilight) rgba(0,0,0, $shadow) rgba(0,0,0, $shadow) rgba(255,255,255, $hilight); }
|
|
|
We've now got fixes for these issues and they will be included in the next update. Thanks for reporting these problems! |
|
|
Another syntax error:
Seems that it is tripping up on the microsoft vendor prefix: i.e.
(This one works fine) filter: formatstring("progid:DXImageTransform.Microsoft.gradient(startColorstr='{0}', endColorstr='{1}')", $color1, $color2); (This one does not) -ms-filter: formatstring("\"progid:DXImageTransform.Microsoft.gradient(startColorStr='{0}', EndColorStr='{1}')\"", $color1, $color2); /* IE8 */
Also, is there a way to turn off sass intellisense? |
|
|
Nevermind on the syntax error part on the last one...If I remove \" then it works fine. One more syntax question:
something like this.. doesn't get colored correctly: background: -moz-linear-gradient(top, $color * 1.05 0%, $color * .95 100%); /* firefox */ |
|
|
I'm still getting squiggles that I don't think I should be getting:
And also:
Both examples compile fine and appear to do what I want them to do.
Also, somebody mentioned turning off SASS intellisense. I think that ability would be great to have. Thanks, keep up the good work! - Chris |
|
|
Another syntax error that I am having is on @font-face -- it compiles fine, but shows a syntax error. @font-face { font-family: 'myfont'; src: url('...');
font-weight:normal; font-style:normal; } |
|
|
Thanks for alerting us to this -- it will be addressed in the next update. |
|