Intellisense Not Functioning for Less Files

I'm currently having some trouble with Web Workbench. When I attempt to open any file ending with .less I don't get any syntax highlighting or intelllisense. I've tried resetting all of my settings and reinstalling workbench repeatedly to no avail.

Edit: After searching through my less markup a bit I found the solution. There was a random comma orphaned near the bottom that was causing the syntax highlighting and intellisense to be turned off. Hopefully this can help some others out.

Should I file a bug report on this? I would think that rather than disabling the entire intellisense/highlighting system it should identify a missing selector?

Thank for reporting this - are you able to send through a copy of an example file which has this problem? We have recently updated the parser to be a bit more forgiving on arbitrary rubbish in the file but this would only be a problem for anything needing to be parsed after the invalid syntax was encountered - not for the whole file so I would be interested in having a look at what is occurring here as adding in an arbitrary comma in a file isn't causing any problems here other than being invalid syntax for compilation.

Thanks!
Jeremy

Sure,

I'm currently running v3.2.419.21172 and this is just a sample file I threw together that causes the issue. The extra comma is after the disclaimer class.

#header { position: relative }

#pageTitle{
    position: absolute;
    overflow: hidden;
    max-height: 3.5em;  
    h1{ font-size: 2em; }
}

.hoverhelp {
    border-bottom:  thin dashed;
    cursor: help;
    position: relative; 
}

.disclaimer,{
    position: absolute;
    display: inline;
    width: 50em;
    left: 20%;
    margin: 0 auto;
    font-style: italic;
    text-align: center;
    font-size: 1.25em;
}

.left { float: left; }
.right { float: right; }
.inline {display: inline;}

EDIT: If I put multiple multi-line comments in it seems to I also found that the syntax highlighting and intellisense are disabled.

for example:

/*html {    
    .backgroundColorFn(@htmlBackgroundColor);
*/
    /*
        comment
    */
    font-size:      100.01%;    
    background-image:   url("../images/background.png");
}

body {
    position:       relative;
    .backgroundColorFn(@bodyBackgroundColor);
    .roundedCorners(5px);
    .boxShadow(0.0em, 0.5em, 1em, darken(@htmlBackgroundColor, 50%));

    /*
        1.0em ~ 10px @ 62.5%
    */
    font-size:      62.5%;
    line-height:        2.75em;
    font-family:        @sansFamily;

    margin:         @spacingSize;
    padding:        0;
}

In this example the comments in the html rule are causing highlighting and intellisense to be disabled for everything below that rule.

Thanks for the extra detail - I have added in a fix for this and this update will be available in the next nightly build. With the comments example, the file itself is actually invalid and is generating a compile error trying to parse the contents, if either comment out the closing brace on the html selector or uncomment the html selector comment the file will become valid enough to compile again and syntax highlighting will also be available.

Jeremy