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 234690 - Value of ng-* attribute incorrectly parsed
Summary: Value of ng-* attribute incorrectly parsed
Status: NEW
Alias: None
Product: web
Classification: Unclassified
Component: AngularJS (show other bugs)
Version: 7.4
Hardware: PC Linux
: P4 normal (vote)
Assignee: Petr Pisl
Depends on:
Reported: 2013-08-21 08:49 UTC by Vladimir Riha
Modified: 2015-09-09 11:41 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

screenshot (61.97 KB, image/png)
2013-08-21 08:49 UTC, Vladimir Riha
sample file to reproduce (1.07 KB, text/plain)
2013-08-21 08:49 UTC, Vladimir Riha

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Riha 2013-08-21 08:49:04 UTC
Created attachment 138971 [details]

Please check the attached screenshot and notice the 3 lines that start with <button. There is data-ng-click directive that calls some function. But first letter is yellow and if I press Ctrl and hover over it, the "f" is not changed to link.

The yellow color happens only with Norway Today, but the problem with Ctrl and hover remains in default NetBeans color scheme

Product Version: NetBeans IDE Dev (Build 201308202300)
Java: 1.7.0_40; Java HotSpot(TM) Client VM 24.0-b55
Runtime: Java(TM) SE Runtime Environment 1.7.0_40-b39
System: Linux version 3.2.0-48-generic-pae running on i386; UTF-8; en_US (nb)
Comment 1 Vladimir Riha 2013-08-21 08:49:27 UTC
Created attachment 138972 [details]
sample file to reproduce
Comment 2 Marek Fukala 2013-08-21 08:59:10 UTC
likely the problem is either in the js embedding provider plugin or in the js support itself. Variables works just fine.
Comment 3 Petr Pisl 2014-01-28 12:48:18 UTC
I don't know, whether is the problem of js lexer, because it's only if the identifier starts with char 'f' or 'd'. The 'f' and 'd' are recognized in the token sequence as number. My guess is that the lexer is in a strange state and resolves this case in wrong way. If you put space before the first char or change the first char, it works correctly.