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 248371 - Single code completion option not autocompleted
Summary: Single code completion option not autocompleted
Status: VERIFIED DUPLICATE of bug 248369
Alias: None
Product: web
Classification: Unclassified
Component: AngularJS (show other bugs)
Version: 8.1
Hardware: PC Linux
: P4 normal (vote)
Assignee: Roman Svitanic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-03 14:44 UTC by Vladimir Riha
Modified: 2014-11-03 15:29 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
sample project (4.81 KB, application/zip)
2014-11-03 14:44 UTC, Vladimir Riha
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Riha 2014-11-03 14:44:33 UTC
Created attachment 150242 [details]
sample project

Please check the attached project:
 - open partial2.html
 - invoke cc on line 20 after the last dot

    <div ng-bind="ct2.dog2.^"></div>

=> code completion offers single option so it should be autocompleted upon code completion invocation but instead code completion is displayed.


Thanks



Product Version: NetBeans IDE Dev (Build 201411030002)
Updates: Updates available
Java: 1.7.0_67; Java HotSpot(TM) Client VM 24.65-b04
Runtime: Java(TM) SE Runtime Environment 1.7.0_67-b01
System: Linux version 3.13.0-35-generic running on i386; UTF-8; en_US (nb)
Comment 1 Roman Svitanic 2014-11-03 15:00:47 UTC
CC for AngularJS is based on JS CC from virtual JS sources and there are available also items from e.g., JS Platform and therefore CC is displayed (and expected do be displayed).
Comment 2 Roman Svitanic 2014-11-03 15:19:50 UTC
I haven't understood correctly what was the real issue.

It should be that if user types e.g., <div ng-bind="ct2.dog2.n^"></div> than the "name" property is autocompleted.

After offline discussion and clarification with Lada we have found out that this issue is effectively the duplicate of bug #248369 and it should be fixed by that fix.

*** This bug has been marked as a duplicate of bug 248369 ***
Comment 3 Vladimir Riha 2014-11-03 15:29:33 UTC
Problem was on my side :) I didn't describe it correctly.  Thanks Romane