| Summary: | The JavaScript launch configuration type can be a bit confusing | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Michael Rennie <Michael_Rennie> | ||||
| Component: | Debug | Assignee: | Project Inbox <jsdt.debug-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Simon Kaegi <simon_kaegi> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | thatnitind | ||||
| Version: | 3.2 | Keywords: | polish | ||||
| Target Milestone: | 3.3 M1 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
applied patch to HEAD |
Created attachment 175519 [details] fix code from HEAD A lot of users see the JavaScript launch configuration and get confused what it really does. Most think it is a single-click type where you create a config and start debugging scripts. I think we need to clearly draw the distinction that this is used to debug remote JavaScript. We could do this by following JDT and renaming it to Remote JavaScript.