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.
Product Version = NetBeans IDE Dev (Build 201308172300) Operating System = Linux version 3.5.0-17-generic running on i386 Java; VM; Vendor = 1.7.0_11 Runtime = Java HotSpot(TM) Client VM 23.6-b04 I have the following html file: <select data-placeholder="{{1+2}}" class="chosen span5" multiple="multiple"> <option value="{{3+3}}"></option> <option>Dallas Cowboys</option> <option>New York Giants</option> <option>Philadelphia Eagles</option> </select> If I type 'data-ng-' inside any of the <option>s, I don't see an autocomplete window. However typing only ng-repeat does show the autocomplete. This should work for data-ng as well as only ng.
Created attachment 139036 [details] IDE log
I assume you mean that it doesn't show up automatically, but if you press Ctrl+Space it does, right? If so, reproducible if one puts caret right after "n" in option and press space Product Version: NetBeans IDE Dev (Build 201308182300) Updates: Updates available 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)
I think it is supposed to work this way. Once you have some data-ng-* attribute used in your code, it opens automatically as with plain ng-*
(In reply to Vladimir Riha from comment #3) > I think it is supposed to work this way. Once you have some data-ng-* > attribute used in your code, it opens automatically as with plain ng-* yes.
Digitman, please confirm Vlada's assumptions or reopen. Thanks for the report.
Ctrl + space should not be required, just typing ng- within a tag, e.g: <option ng- causes the autocomplete to show up, without the need for ctrl + space. However, if you type the following: <option data-ng- then the autocomplete doesn't show up as expected (it may show up after ctrl + space, but it should show up automatically as it does for plain ng- attributes).
On further testing, it seems that if the file contains one previous angularjs tag, then the autocomplete works for the future tags, but for the first tag within a file, it works for ng- attributes (without ctrl + space) but doesn't work for data-ng- attributes.
yep, that's exactly what Vlada mentioned in comment#3 and what is the designed behaviour. The reason is that we do not want to spoil the completion window with all the possible notations so the completion behaves according to the notation used in the file. The drawback you've explored is that for the first time you need to type it w/ the completion help. This minor issue can possibly be removed, if you insist on that I can change this to enhancement and fix that bit later. I personally consider this a very minor problem though.