58413 - [RFE] Javascript/XUL run-time environment/debugger

Status: VERIFIED FIXED

(Other Applications Graveyard :: Venkman JS Debugger, enhancement, P3)

Description

[Brian 'netdragon' Bober]

Here is another of my ideas - hope you like it:

There needs to be a better javacript debugger where one can set breakpoints,
single step, view variables, look at the DOM, etc. All these could be included
on the javascript console window or under Debug in the Mozilla window. It would
work on any part of Mozilla that uses Javascript - such as chatzilla or mailnews.

Comment 1

[John Bandhauer]

Well, ya. Do you have someone lined up to do the work?

Comment 2

[Brian 'netdragon' Bober]

I was thinking you :-) 
Seriously - this could be a future. Maybe for non-beta release 1 or the last 
beta.

Comment 3

[timeless]

see also Netscape Visual Javascript (java), MSScript Debugger (com), 
ActiveState Komodo (xpcom).

Is this a dupe of komodo ;-?

Comment 4

[Brian 'netdragon' Bober]

I meant javascript. This would be a way to debug javascript in web pages.

Comment 5

[djoham]

I would be more than happy to "do the work" if the hooks into the engine were
already there. It's my understanding though that a lot of C/C++ hacking needs to
take place before there's any real hope of getting this done.

I'll make folks a deal. If the C++ stuff gets done and documented, I'll do the
UI part of it. Howsaboutit?

What would even be cooler is if we could step through the HTML as it was being
sent to the parser.

Do we have any takers?

Comment 6

[Brian 'netdragon' Bober]

Yeah that would be really cool cause sometimes you don't know why something is 
loading before something else, or something is not working correctly in HTML. 
Should we create another bug for that?

Comment 7

[Brian 'netdragon' Bober]

Actually, what this would come in really handy for is debugging the chrome. It 
would also cut tons of development time off of people's work. Therefore, 
spending some of people's time on this will create a lot of time for people in 
the future and make this project move a lot faster.

Comment 8

[Brian 'netdragon' Bober]

With the Document Inspector source in the tree now (I think), are the hooks 
there now?

Comment 9

[Brian 'netdragon' Bober]

Sorry, URL: http://www.joehewitt.com/inspector/releasenotes.html

Comment 10

[Joe Hewitt (gone)]

Document Inspector will certainly be a step in the right direction, but it's
certainly not a Javascript debugger (yet).  It's not checked in yet because I've
 yet to find a Mac engineer willing to take the time to help setup the mac build
scripts for the project.  Once someone volunteers to help, I will have
permission to check it in from mozilla.org

Comment 11

[John Bandhauer]

reassign to rginda

Comment 12

[Robert Ginda]

I'm going to mark this fixed.  We're working on it, no need to keep a bug open
for it.

Comment 13

[Brian 'netdragon' Bober]

Cool stuff.