User:GijsKruitbosch/JS Debugging: Difference between revisions

User:GijsKruitbosch/JS Debugging (view source)

Revision as of 06:48, 18 May 2006

315 bytes removed , 18 May 2006

venkman already does persistent state thing

GijsKruitbosch

Confirmed users

290

edits

@@ Line 1: / Line 1: @@
 Things I've heard so far:
-* Persist state [in context of xulrunner?] - give functionality to save and delete a dump of the watches and breakpoints set, and auto-load that at debugger startup so you can continue with whatever you were doing before you last closed the debugger for that app. Could this be done URL-based for website stuff? (talking to Daniel Glazman)
+* Persist state (Daniel Glazman) - do we have this already? It seems so... need more details.
 * Give direct access to profiling data - right now you can save it as html or text, but you can't view it directly (or so I was told, haven't verified this). If you're debugging and don't want to let go of the browser which is stopped, then that's a problem because you need that browser to view your profile output. Which is kinda odd and confusing and not really a Nice Thing. (talking to Hish)
 * Anonymous functions get lumped together when profiling. Baaaad. On the other hand, you can just rename the functions yourself...
@@ Line 13: / Line 13: @@
 * Give access to the DOM Inspector if you have a variable which is referencing an element in the page.
 * Provide a real js console to evaluate expression and actually have an effect on the website, instead of the lousy functionality of the current console.
-* Better XBL debugging (this is outside the scope of a web development thing too, perhaps?). Daniel Glazman named a few weird bugs - need to check if they've been filed.
+* Better XBL debugging. Daniel Glazman named a few weird bugs - need to check if they've been filed.