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 233216 - CSS Error: Warning when url value token used in background parameter.
Summary: CSS Error: Warning when url value token used in background parameter.
Status: RESOLVED DUPLICATE of bug 233038
Alias: None
Product: web
Classification: Unclassified
Component: CSS Preprocessors (SASS, LESS, ...) (show other bugs)
Version: 7.4
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Marek Fukala
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-22 20:26 UTC by indesignfirm
Modified: 2013-07-23 06:27 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Screenshot of warning (45.52 KB, image/jpeg)
2013-07-22 20:26 UTC, indesignfirm 		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 indesignfirm 2013-07-22 20:26:55 UTC 
Created attachment 137588 [details]
Screenshot of warning

The editor mark as an error when the url() method is used inside any background
parameter, ex. background or background-image, suggesting the code in not in
compliance.

This only seems to happen when editing in a SCSS file where we are appending data to a dynamic variable.  IE url($ImagesPath+'bridge_bg.jpg')

There error that we are receiving is Unexpected Token COLON Found.  If we remove tick marks or quote marks, the error goes away, however that isn't syntactically correct.  This is very similar to bug #209586
Comment 1 Ondrej Brejla 2013-07-22 20:48:03 UTC 
Reassigning.
Comment 2 Vladimir Riha 2013-07-23 06:25:54 UTC 
Reproducible, I think this is the same problem as #2 in issue 233038, usage of url() and $variable. Thank you for reporting

Product Version: NetBeans IDE Dev (Build 201307222300)

*** This bug has been marked as a duplicate of bug 233038 ***
Comment 3 Vladimir Riha 2013-07-23 06:27:50 UTC 
(In reply to comment #2)
> I think this is the same problem as #2 in issue 233038

Sorry, I've meant #1, the one in description.