119827 - Need to prevent users from exiting debug target while stopped

Status: RESOLVED FIXED

(Other Applications Graveyard :: Venkman JS Debugger, defect)

Description

[Christopher Aillon (sabbatical, not receiving bugmail)]

Steps to reproduce on Linux 2002011108:

0. Have Venkman ready to pick up new JS files (eg, init at startup turned on)
1. Edit > Preferences > Privacy > Cookies > View Stored Cookies.
2. Set a breakpoint within CookieSelected() in CookieViewer.js
3. Select a cookie.  The breakpoint is activated.
4. Cancel or close cookie viewer.

Actual results: We are still at the breakpoint in the halted state.

Expected results: We should exit out of the breakpoint, as if execution has
finished.

Comment 1

[Robert Ginda]

I'm not so sure about that.  I think maybe the debug target should be disabled
while you're stopped.  Not only should this prevent you from closing the window,
it should also stop you from interacting with the window in any fashion.

Comment 2

[Christopher Aillon (sabbatical, not receiving bugmail)]

That is an alternative which I hadn't thought of too.  I actually like that idea
better.

Please fix not being able to debug modal windows first though (bug 100677). 
That would lead to some interesting situations :)

Comment 3

[Robert Ginda]

re: modal debugging, Good Point.

I've got code which turns off js on the window while it is stopped, but that
doesn't keep the user from dismissing a window via a windowmanager widget of
some sort.  I'll need to think of something else there.

Comment 4

[scottputterman]

Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+,
topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword.  Please send any
questions or feedback about this to [e-mail].  You can search for
"Moving bugs not scheduled for a project" to quickly delete this bugmail.

Comment 5

[Robert Ginda]

I checked in the venkman changes to make this work in bug 100677.  Linux users
will have to wait for bug 129591, all other platforms should be fixed.

Comment 6

[Robert Ginda]

if bug 129591 get's fixed for 1.0, this will too.  It doesn't look like 129591
is going to make it, so speak up now if you care.

Comment 7

[Robert Ginda]

fixed by check-in for bug 129591