Community
Participate
Working Groups
Build ID: Build id: M20060921-0945 Steps To Reproduce: The javascript editor and outline view are not informative with the following pattern of object-oriented javascript. function BTRNMName() { this._data = 0; this._entityType = 0; this._entityUID = 0; this._extra = 0; this._language = 0; this._primary = 0; this._script = 0; this._transliterations = []; this._uid = 0; } BTRNMName.prototype.getData = function(){ return this._data; } BTRNMName.prototype.setData = function(val){ this._data = val; } More information:
Yes, unfortunately we do not (and never intended to) support OO Javascript. It would be great to do so, but unfortunately we have no people to do so and no plans to. I'll count this as an enhancement request instead of a bug per se.
It should support ECMAScript syntax. So it's definitely a bug and not an enhancement.
Setting aside the severity debate, we just don't have people to work on this now. We would accept high quality patches, though.
I'm doing a mass resolve of all open bugs in the wst.javascript component. Resolving to "won't fix". The reason is that the old wst.javascript component is being removed this release, and replaced by the wst.jsdt component. So ... if any owners of these wst.javascript bugs see the same problem in the wst.jsdt code, then please open a new bug on that component. Apologies we can't check each ourselves, but there's just too many (and too few people) so we'll need community help. Just glancing, I know for sure many will no longer be bugs but some may still be legitimate requests even in the new JSDT code.
