Bugzilla – Full Text Bug Listing
| Summary: | Properly scope variables | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Michael Rennie <Michael_Rennie> | ||||
| Component: | Debug | Assignee: | Project Inbox <jsdt.debug-inbox> | ||||
| Status: | NEW --- | QA Contact: | Simon Kaegi <simon_kaegi> | ||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | thatnitind | ||||
| Version: | 3.2 | ||||||
| Target Milestone: | Future | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 322861 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
Created attachment 167741 [details] screen shot code from HEAD If you run a variety of scripts the variables view can become quite confusing over time. In the attached screen shot you can see that most of the variables shown in the view do not apply to what is being debugged - they are variables from other scripts that have been debugged earlier, but which are still loaded in the global scope.