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
|
Hi! I've got this piece of valid CSS code in my project:
LESS marks this as a syntax error and fails to compile. I'm not sure if this is a problem on your side or on the side of dotLess. I would be nice to have this fixed though. LESS also marks gligoran |
|
|
Hi gligoran, Things that don't compile are issues in the Less compiler, which I'm afraid it outside our control. We don't use dotLess, but the JavaScript Less compiler from http://lesscss.org/ -- you can raise issues with this at https://github.com/cloudhead/less.js. Things that are incorrectly marked as syntax errors in Visual Studio are Web Workbench issues. We did have a bug with incorrect highlighting of the @page directive in 2.x, but that should be fixed in 3.0. Can you post a small snippet that exhibits the @page directive error? Thanks! We will also take a look at the highlighting of your selector. |
|
|
I've posted an issue with lesscss. I've also attached a file which shows how Here's the code:
|
|
|
Thanks. We've reproduced this issue and should have a fix for you soon. However, that second @page directive in the @media rule, without any braces after it, looks a bit odd to us. The references I've seen all indicate that @page must have a margin ruleset. Is your understanding that the margin ruleset is optional, or is this just a typo? |
|
|
Oh, forgot about that, I was just trying to see it @page (without { and }) got highlighted the same way inside and out side @media. Tried putting 2 @page blocks with margin rulesets and there was no syntax error. My bad. Hope you fix the other cases soon though :) |
|
|
Hi gligoran, We've been checking on that @= selector and as far as we can tell we are right to flag it. According to http://www.w3.org/TR/css3-selectors/#attribute-selectors an attribute selector can include =, ~=, |=, ^=, $= or *=, all of which we support. Is it an extension that isn't part of the standard? |
|
|
Just to let you know, the @page fix will be in the next nightly build. We're holding off on the @= issue until we're sure it's what you intended. The nightly build will be available from about 1200 GMT -- for download instructions see http://www.mindscapehq.com/forums/thread/281069. |
|
|
Great to hear that you already fixed the Regarding the Also, I just noticed that auto-formatting doesn't work in -gligoran |
|
|
Thanks for letting us known about the @media formatting issue. This will be fixed in the next nightly build. |
|