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 190945 - Javascript navigator do not show functions declared as variables
Summary: Javascript navigator do not show functions declared as variables
Status: NEW
Alias: None
Product: javascript
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal with 1 vote (vote)
Assignee: Petr Pisl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-12 12:55 UTC by dziastinux
Modified: 2014-01-16 10:26 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
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 dziastinux 2010-10-12 12:55:47 UTC 
How to reproduce:
1. Create new JavaScript file
2. Paste following code:
function a1(){};
var b1 = function(){};
3. Notice that only a1 function appears in JavaScript Navigator.

Product Version = NetBeans IDE 6.9.1 (Build 201007282301)
Operating System = Windows 7 version 6.1 running on x86
Java; VM; Vendor = 1.6.0_21
Runtime = Java HotSpot(TM) Client VM 17.0-b17
Comment 1 Marian Mirilovic 2011-03-25 23:19:17 UTC 
Please evaluate : if you do not plan to fix it for NB 7.0 ask for waiver ASAP.
Comment 2 Marek Fukala 2011-03-28 13:15:34 UTC 
Reproducibe even in 7.0 dev. I seriously doubt it ever worked as requested. The navigator does show the b1 as variable which is actually not wrong. In any case I do not see a single argument for this being P2.
Comment 3 bht 2011-05-04 17:43:29 UTC 
AFAIK Navigator does not reflect state of the program after program execution  / assignments.

Enhancement if not invalid.
Comment 4 Marek Fukala 2011-05-05 09:28:37 UTC 
(In reply to comment #3)
> AFAIK Navigator does not reflect state of the program after program execution 
> / assignments.
> 
> Enhancement if not invalid.

I believe there was at least an attempt to do so. For example the refactoring does some type analysis on the code and AFAIK uses the type from the last assignment.