User:GijsKruitbosch/JS Debugging/Tasks: Difference between revisions
(Moving stuff to w.m.o) |
|||
| Line 175: | Line 175: | ||
</tr> | </tr> | ||
</table> | </table> | ||
I would probably order these things higher: | |||
* immediate profiling | |||
* newlines in watches view (but there's no watch support yet, so?) | |||
* eval JS in tab/frame/etc. | |||
And these things lower: | |||
* JS 1.7 | |||
* inline function editing | |||
But I think you're generally on the right track. I need to write here how we can track what document an error came from without biting off everything that's in the current bug 228205, too. Basically involves finding the current document (via cx->contextPrivate->scriptOwner->frameElement or some such) from the handler called for exceptions and errors, and keeping track of it. We could also "just" have the console error object QI to nsIException, but I bet that would make some people API-sad, so I'm interested in us keeping the hacks to our side of the line if we can. | |||
-- shaver | |||
Revision as of 19:14, 15 June 2006
Importance-ordered Task List
A small note about this list: importance != working order, given that some of these items need other items, and that some require back-end changes which will need to happen fast, if at all, on the 1.8.1 branch (which is what I'm trying to cater to).
Front end work is being done on: Firebug
| N | Task | Needs backend changes | Bug number | Result |
| 1 | Implement list of Breakpoints | No | - | None yet |
| 2 | Implement Watches | No | - | None yet |
| 3 | Backend for nsIScriptError to report the document an error came from - Wait... this will probably be too big/complicated to get right on 1.8... | Yes | bug 228205 | None yet |
| 4 | Frontend adapted to keep breakpoints and such separate on a per-document basis (see above) | Yes | bug 228205 | None yet |
| 5 | Be able to go from a var referencing a DOM element to that DOM element in DOMI | Yes? | - | None yet |
| 6 | Be able to debug from the slow script warning dialog. | Yes? | - | None yet |
| 7 | Changing variable values / evaluating js shouldn't require changing tabs away from the debugger (in Firebug) | No | - | None yet |
| 8 | Anonymous functions should not be lumped together in profiling. | Presumably not | - | None yet |
| 9 | Newlines are lost in the watches view. | No | - | None yet |
| 10 | Double-check handling of about:blank and (related) running/stopped state tracking in Firebug. | No | - | None yet |
| 11 | JS 1.7 improvements | Yes? | - | None yet |
| 12 | Figure out why I'm crashing on GMail with firebug enabled (hack/sneak/workaround?) | Hopefully not. | - | None yet |
| 13 | Provide immediate access to profiling data | No | - | None yet |
| 14 | Evaluate js in different windows/tabs/iframes | No | - | None yet |
| 15 | Fix wrapping of variable/value tree | No | - | None yet |
| 16 | Inline editing of functions etc. | No, hopefully. | - | None yet |
| 17 | Debug mutation events (watch DOM elements) | Yes | - | None yet |
| 18 | Getters / Setters improvements | Yes? | - | None yet |
| 19 | 'real' stack list (not a dropdown) | No | - | None yet |
| 20 | Pretty print | No | - | None yet |
I would probably order these things higher:
- immediate profiling
- newlines in watches view (but there's no watch support yet, so?)
- eval JS in tab/frame/etc.
And these things lower:
- JS 1.7
- inline function editing
But I think you're generally on the right track. I need to write here how we can track what document an error came from without biting off everything that's in the current bug 228205, too. Basically involves finding the current document (via cx->contextPrivate->scriptOwner->frameElement or some such) from the handler called for exceptions and errors, and keeping track of it. We could also "just" have the console error object QI to nsIException, but I bet that would make some people API-sad, so I'm interested in us keeping the hacks to our side of the line if we can.
-- shaver