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 253242 - CSS unicode-range rule line highlighted as "parsing error"
Summary: CSS unicode-range rule line highlighted as "parsing error"
Status: NEW
Alias: None
Product: web
Classification: Unclassified
Component: CSS Editor (show other bugs)
Version: 8.2
Hardware: PC Windows 10 x64
: P3 normal with 5 votes (vote)
Assignee: Milutin Kristofic
URL:
Keywords:
: 257303 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-06-29 16:01 UTC by nskforward7
Modified: 2017-12-08 13:14 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Snapshot of error (124.77 KB, image/png)
2015-06-29 16:01 UTC, nskforward7
Details
Screenshot of parser error (29.89 KB, image/png)
2016-02-24 18:08 UTC, p0lar_bear
Details
Screenshot of error in NB8.2 (11.90 KB, image/png)
2017-03-14 14:54 UTC, ShuffleBits
Details

Note You need to log in before you can comment on or make changes to this bug.
Description nskforward7 2015-06-29 16:01:55 UTC
Created attachment 154431 [details]
Snapshot of error

/* I created new css file with body like: */

@font-face {
  font-family: 'Open Sans';
  font-style: normal;
  font-weight: 300;
  src: local('Open Sans Light'), local('OpenSans-Light'), url(../fonts/DXI1ORHCpsQm3Vp6mXoaTa-j2U0lmluP9RWlSytm3ho.woff2) format('woff2');
  unicode-range: U+0460-052F, U+20B4, U+2DE0-2DFF, U+A640-A69F;
}



/* "unicode-range" line highlighted as "parsing error" (see attachment) */
Comment 1 Echo89 2016-01-18 09:49:30 UTC
I am also seeing the same error.
Comment 2 p0lar_bear 2016-02-24 18:02:07 UTC
*** Bug 257303 has been marked as a duplicate of this bug. ***
Comment 3 p0lar_bear 2016-02-24 18:08:14 UTC
Created attachment 158637 [details]
Screenshot of parser error

Still having this issue in netbeans 8.1. It doesn't seem to know how to handle characters coming after the hyphen when a range is used.

Note that an exact copy of the at-rule but with the ranges removed doesn't trigger the parser error.
Comment 4 Xylane 2016-09-03 14:29:37 UTC
Any news regarding a fix? I still see the issue on 8.2 nighty build.
Comment 5 suryana-itc 2016-10-29 04:13:40 UTC
+1
Comment 6 mathieu_sopheos 2016-12-15 15:27:36 UTC
Same error in css files and in less files
Comment 7 ShuffleBits 2017-03-14 14:54:15 UTC
Created attachment 163831 [details]
Screenshot of error in NB8.2
Comment 8 matup 2017-11-30 21:08:43 UTC
+1 please vote