Note: While whittling down my code to a small demonstration of the bug, I realized that I had marked a non-public method with "@public". Removing the annotation removes the formatting issue, but I suspect there's still a bug in the JSDoc usage.

In the following code the "@public" annotation causes one reference to the function "foo" to erroneously appear as a global function (and breaks navigation) but not the other. Only the one that access a property of the function's return value.

    (function () {
        /**
         * @public                  // this doesn't belong here
         */
        function foo() {
            return 'foo';
        }

        function bar() {
            return foo().length;    // "foo" has the global variable color
        }

        function baz() {
            return foo();           // this "foo" is fine
        }
    }());

If NetBeans is smart enough to detect that "foo" should not be marked as "@public", it should display a warning on that line.