This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 242764 - SCSS parser errors
Summary: SCSS parser errors
Status: RESOLVED WORKSFORME
Alias: None
Product: web
Classification: Unclassified
Component: CSS Preprocessors (SASS, LESS, ...) (show other bugs)
Version: 8.0
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: issues@web
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-11 02:13 UTC by squarestar
Modified: 2014-05-12 08:17 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE log (258.66 KB, text/plain)
2014-03-11 02:14 UTC, squarestar 		Details
Example of scss file with parse errors (3.72 KB, text/scss)
2014-03-11 02:36 UTC, squarestar 		Details
Correct example file with parse errors (1.78 KB, text/scss)
2014-03-11 02:43 UTC, squarestar 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description squarestar 2014-03-11 02:13:53 UTC 
Product Version = NetBeans IDE 8.0 RC1 (Build 201402242200)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.7.0_13
Runtime = Java HotSpot(TM) 64-Bit Server VM 23.7-b01
SCSS files are displaying errors where there are none. For example, "Unexpected token WS found" being displayed after an "@include" directive, or a valid HTML element being flagged as an "unknown property".

Editor-folds are not working in SCSS files.
Comment 1 squarestar 2014-03-11 02:14:00 UTC 
Created attachment 145923 [details]
IDE log
Comment 2 squarestar 2014-03-11 02:36:18 UTC 
The attached file shows an example of one of the errors in my first comment - the "unknown property" on line 60 ("li") I also noticed that code highlighting styles are not being correctly appied to the elements from line 60 to 65. However, I had an error on line 64 (missing closing parenthesis) which seems to have been causing the WS error, though the parser was not displaying the correct error.

The highlighting and "unknown property" errors seem to be related to the use of the colon after an element (though not after the "&" placeholder). There is a mixin at the end which also incorrectly displays unexpected token errors for the colon.
Comment 3 squarestar 2014-03-11 02:36:21 UTC 
Created attachment 145924 [details]
Example of scss file with parse errors
Comment 4 squarestar 2014-03-11 02:43:38 UTC 
Sorry, attached the wrong file previously. Please remove if possible.
Comment 5 squarestar 2014-03-11 02:43:40 UTC 
Created attachment 145925 [details]
Correct example file with parse errors
Comment 6 Vladimir Riha 2014-05-12 08:17:17 UTC 
Are you sure the 2nd file is valid? On line 64, there is missing ), 

@include TextShadow(0, -1px, 1px, rgba(0, 0, 0, .3);

but should be

@include TextShadow(0, -1px, 1px, rgba(0, 0, 0, .3));

The 3 lines 75-77, shouldn't it be more like a 

	$eot: quote(#{$fileHandle}+".eot");
	$woff: quote(#{$fileHandle}+".woff");
	$ttf: quote(#{$fileHandle}+".ttf");

? Could you please attach full sample that could be compiled to CSS? (your sample is missing e.g. TextShadow mixin). Even when I removed the TextShadow usage, compiler still complains about the lines 75-77 (the fix above removes this issue)

Syntax error: Invalid CSS after "...(#{$fileHandle}": expected ")", was ".eot);"