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 241480 - Unexpected token COLON found in @font-face src and @mixin background-image
Summary: Unexpected token COLON found in @font-face src and @mixin background-image
Status: RESOLVED DUPLICATE of bug 238988
Alias: None
Product: web
Classification: Unclassified
Component: CSS Preprocessors (SASS, LESS, ...) (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: issues@web
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-06 10:07 UTC by luke83
Modified: 2014-02-13 08:03 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
sass1 (49.52 KB, image/png)
2014-02-06 10:07 UTC, luke83
Details
sass2 (40.89 KB, image/png)
2014-02-06 10:07 UTC, luke83
Details

Note You need to log in before you can comment on or make changes to this bug.
Description luke83 2014-02-06 10:07:14 UTC
i got "Unexpected token COLON found" with this code:

@mixin img-retina($file-1x, $file-2x, $width-1x, $height-1x) {
  background-image: url(if($bootstrap-sass-asset-helper, twbs-image-path("#{$file-1x}"), "#{$file-1x}"));

and this one also

@font-face {
  font-family: 'Glyphicons Halflings';
  src: url(if($bootstrap-sass-asset-helper, twbs-font-path('#{$icon-font-path}#{$icon-font-name}.eot'), '#{$icon-font-path}#{$icon-font-name}.eot'));
  src: url(if($bootstrap-sass-asset-helper, twbs-font-path('#{$icon-font-path}#{$icon-font-name}.eot?#iefix'), '#{$icon-font-path}#{$icon-font-name}.eot?#iefix')) format('embedded-opentype'),

as you can see in the attachments.

But the sass compilation is fine and the output file is correct. The sass source is from bootstrap-sass github project with no modification.
Comment 1 luke83 2014-02-06 10:07:41 UTC
Created attachment 144861 [details]
sass1
Comment 2 luke83 2014-02-06 10:07:57 UTC
Created attachment 144862 [details]
sass2
Comment 3 Ondrej Brejla 2014-02-12 14:01:51 UTC
Probably "URI" should be processed not in lexing part, but in parsing part. Right now URI consists only from '(' URL | STRING ')'...exact tokens.
Comment 4 Vladimir Riha 2014-02-13 08:03:36 UTC
Seems like the same as in 238988

*** This bug has been marked as a duplicate of bug 238988 ***