| Summary: | [language support] Defining constructor by assignment leaks properties to global object | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Laurens Holst <laurens.nospam> | ||||
| Component: | General | Assignee: | wst.javascript <wst.javascript-inbox> | ||||
| Status: | RESOLVED WORKSFORME | QA Contact: | Nitin Dahyabhai <thatnitind> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | cmjaun | ||||
| Version: | 3.2 | ||||||
| Target Milestone: | Future | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
I do not see this problem in the 3.5 drivers. |
Created attachment 155138 [details] Testcase Using Eclipse 3.6.0M4 and WTP 3.2.0M4. When defining a constructor by assignment, the properties set in the constructor appear on the global object. See the attached testcase.