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 250012 - (wrong) CSS parser error within JSF-projects with EL-expressions
Summary: (wrong) CSS parser error within JSF-projects with EL-expressions
Alias: None
Product: web
Classification: Unclassified
Component: CSS Editor (show other bugs)
Version: 8.0.2
Hardware: PC Windows 8 x64
: P3 normal with 3 votes (vote)
Assignee: Milutin Kristofic
Depends on:
Reported: 2015-01-25 14:03 UTC by raelianer
Modified: 2015-08-02 15:51 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description raelianer 2015-01-25 14:03:37 UTC
Product Version: NetBeans IDE 8.0.2 (Build 201411181905)
Java: 1.7.0_65; Java HotSpot(TM) 64-Bit Server VM 24.65-b04
Runtime: Java(TM) SE Runtime Environment 1.7.0_65-b19
System: Windows 8 version 6.2 running on amd64; Cp1252; de_DE (nb)
User directory: C:\Users\Username\AppData\Roaming\NetBeans\8.0.1
Cache directory: C:\Users\Username\AppData\Local\NetBeans\Cache\8.0.1

Parser reports error "Unexpected token COLON found" at

Code is from the primefaces showcase:

Probably related bug reports:
Comment 1 Vladimir Riha 2015-01-26 09:22:03 UTC
Reproducible, but I think the error is correct here. This is a plain CSS file where this syntax is not valid (unlike issue 246822 which is about Sass). You can hide the error if you click on the bulb icon next to the marked line (but it just hides the error badge)
Comment 2 raelianer 2015-01-26 11:21:54 UTC
I'd say this is not a plain CSS-file.
I think it's like Sass, there are EL-expressions that will be replaced before the file is delivered to the client. Maybe it's possible to use a different parser or parsing settings within a JSF-project? Therefore I'm setting the issue type to "enhancement" and reopen the request.

I wish I could hide that type of error only within that file and not in all of them. But ignoring that file will be enough or now, thanks!
Comment 3 99sono 2015-08-02 15:51:04 UTC

It is not a plain css file, however, if the value expression is well formed and it will be parsed and the CSS file will - in the end  ultimately valid, ideally the line should not be marked as an error.

It is not a "must-have" rather, it is just a  "nice-to-have" thing.