Please give it try in Dev build from [1] or (older) 8.0 Beta. The results in 8.0 RC1 are following (assuming NoArgs means "suggested as property not function")


                                  8.0 RC1      
myObj.doMyObjMethod()               OK       
myObj2.doMyObjMethod()              N/A      

myExObj.doMyObjMethod()             OK       
myExObj.doExMethod()                NoArgs   

myEx2Obj.doMyObjMethod()            OK       
myEx2Obj.doExMethod()               NoArgs   
myEx2Obj.doEx2Method()              OK       
myEx2Obj.doEx2MethodFromMyObj()     NoArgs   
myEx2Obj.doEx2MethodFromEx()        NoArgs   



Simple case to reproduce the "suggested as property not function" is following:

function test(){
    window.console.log(1);
}

var foo = {};
foo.bar = test;
foo.bar();


=>foo.bar is considered to be property not function in code completion and Navigator.



[1] bits.netbeans.org/netbeans/trunk/nightly/latest/



Product Version: NetBeans IDE 8.0 RC1 (Build 201402242200)
Java: 1.8.0; Java HotSpot(TM) Client VM 25.0-b69
Runtime: Java(TM) SE Runtime Environment 1.8.0-b129
System: Linux version 3.2.0-48-generic-pae running on i386; UTF-8; en_US (nb)

Got the same result on older version of 8.0 - NetBeans IDE 8.0 Beta (Build 201401141042),  this means that there is regression in Javascript Intellisense of 'Development' version.

I was thinking that development version will turn into IDE 8.0 final soon. Where did you get 8.0 RC1? I see only 8.0 Beta on download page (https://netbeans.org/downloads/), which is the one I have already.

RC1 is not yet released, but it should be in couple of days

I have tested the library file in different situation (in anonymous function, in global scope etc. and my results corresponds to the Vlada's result.

I don't see here any regression. I can be wrong.

The problem with the function treated as property - I don't know, whether I can fix it in NB 8.0 do to the complex fix. I'm going to look at this more.

I just rechecked and it appears that either I was testing 'dev' version in a some wrong way or there was something wrong with my installation. Currently I've got intellisense in 'dev' working indeed the same way as in 8.0 Beta and described by Vladimir Riha.


Meanwhile I've noticed more use-cases where intellisense does not work
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

function ThisLib() {
    /** @constructor */
    function MyObj() {
        this.doMyObj = function(arg) {}
    }
    
    this.MyObj = MyObj;
    
    /**
     * @returns {ThisLib.MyObj}
     */
    this.getMyObj = function getMyObj() { return new MyObj(); }
};
var thisLib = new ThisLib();

// (2.1) !!!! no intellisense after thisLib. here !!!!!
var myObj = new thisLib.MyObj();

// (2.2) OK
var myGetObj = thisLib.getMyObj();

// (2.3) OK
myGetObj.doMyObj();


var protoLib = new ProtoLib();

function ProtoLib() {
    /** @constructor */
    function MyPObj() {}
    
    MyPObj.prototype.doMyPObjMethod = function (arg) {}
    
    ProtoLib.prototype.MyPObj = MyPObj;
    
    /**
     * @returns {MyPObj}
     */
    ProtoLib.prototype.getMyPObj = new function () { return new MyPObj(); };
};

// (2.4) OK - In this case intellisense knowns about MyPObj
var myNewPObj = new protoLib.MyPObj();

// (2.5) !!!! no intellisense after myNewPObj. here !!!!!
myNewPObj.doMyPObjMethod();

var myGetPObj = protoLib.getMyPObj();

// (2.6) OK
myGetPObj.doMyPObjMethod();

ProtoLib.prototype.getMyPObj = new function () { return new MyPObj(); };
should be changed to
ProtoLib.prototype.getMyPObj = function () { return new MyPObj(); };

I have separated the Vlada's simple case to the issue #242408. This issue is more complex.

As the current status from 'clients' - the most annoying bugs to me are buggy cases (1) and (3) below. It would be nice if the can be fixed sooner than later.
The strange thing is - I've tested against Dev (Build 201402280001) and case (3) is still reproducible, where as it looks to be the some one as in already fixed https://netbeans.org/bugzilla/show_bug.cgi?id=242408 "Function is treated as property".

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 


var myLib = new function MyLib() {
    /**
     * @constructor
     * @returns {MyLib.MyObj}
     */
    this.MyObj = function() {
        /** @member {string} My Description */
        this.member = "value";
    };
    
    /**
     * @returns {MyLib.MyObj}
     */
    this.newMyObj = function MyLib_newMyObj() { 
        return new this.MyObj();
    };
    
    /**
     * ShareableFunc
     * @param {string} arg description
     */
    function PublicAndPrivateUsageFunc(arg) {}
    
    this.publicInnerFunc = PublicAndPrivateUsageFunc;
    
    /**
     * My Description
     * @param {string} arg My Argument
     */
    this.publicFunc = function MyLib_publicFunc(arg) { }
};

// (1) Intellisense does NOT work on myObj.member - not good
var myObj = new myLib.MyObj();
myObj.member;

// (2) Intellisense DOES work on myNewObj.member - good.
var myNewObj = myLib.newMyObj();
myNewObj.member;

// (3) Intelisense DOES NOT recognize it as refernce on
//     function "PublicAndPrivateUsageFunc()" within MyLib
//     Note: this is similar case to (FIXED)
//           https://netbeans.org/bugzilla/show_bug.cgi?id=242408
//           but is still reproducible
myLib.publicInnerFunc();

// (4) Intellisense works correctly here 
//     and case #3 is expected to work the same way 
myLib.publicFunc();

Thanks for your cooperation. It's always good to have the test cases :).

I have separated the case 3 to the issue #242454. It's different from issue #242408, which solves basically only functions not "methods".

Not sure what has changed in JS support in Netbeans during last year, but ... use-case #2 (myNewObj.member;) does not work anymore.

Additionally, trying to make a stubbed version of my js lib cross-usable between Netbeans and WebStorm i see there are problems in both, but NetBeans fails in more simple/standard cases.

Here is one more use-case - intellisense partially does not work for properties in 'b1' object(the last line). See screenshot for more details.

- - - - - - - - - - - - 

/** Implementation of the MyLib Library */
var MyLib = new function MyLib() {};

/** @constructor
 *  @returns {MyLib.ObjA} description */
MyLib.ObjA = function (arg) {
    /** JsDoc for MyLib.ObjA.aproperty
     * @type {number|string} */
    this.aproperty = this.aproperty;
};

/**
 * Constructs MyLib.ObjA
 * @returns {MyLib.ObjA}
 */
MyLib.objA = function () {
};

/** @constructor
 *  @returns {MyLib.ObjB} description */
MyLib.ObjB = function (arg) {
    /** JsDoc for MyLib.ObjB.aproperty
     * @type {number|boolean} */
    this.aproperty = this.aproperty;
};

/** Constructs MyLib.ObjB
 *  @return {MyLib.ObjB} */
MyLib.objB = function () {
    return new MyLib.ObjB();
};

var a2 = new MyLib.ObjA();
var res = a2.aproperty;

/** @type MyLib.ObjA */
var a1 = MyLib.objA();
var res = a1.aproperty;

var b2 = new MyLib.ObjB();
var res = b2.aproperty;

var b1 = MyLib.objB();
var res = b1.aproperty;

Created attachment 153166 [details]
netbeans-jsdoc-bugs.png

This issue contains more issues and starts to be chaotic. We need to separate every case into the different issue. It's better then to treat it. 

I have split the previous comment into issue #251819, issue #251820 and issue 251821. If I miss something, please create new issue for it. 

Also if something missing from the previous case. I would like close this issue and solve the cases separately. Thanks.

Re: This issue contains more issues and starts to be chaotic. We need to separate every case into the different issue. It's better then to treat it. 

'chaotic' - yes, too much in on place, though it is hard from my perspective to 'correctly' create sub-issues as I do not have internal knowledge about Netbeans' implementation. For me it looks to be more or less the same :)


Re: I would like close this issue and solve the cases separately.

I'm OK with that, hoping that things will work correctly in general.

Thanks, I close this issue as fixed, even if there are probably cases that still doesn't work. But the bulk of these are already fixed. 

If you run in a case, which doesn't work, please enter separate issue for it. It's much better to treat separate cases and more cases in one issue. Thanks.