My favorites | Sign in
Project Home Wiki Issues
New issue   Search
  Advanced search   Search tips   Subscriptions
Issue 1575: New watch expression can't be created when breakpoint is active
3 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Closed:  Apr 2009

Sign in to add a comment
Project Member Reported by, Mar 10, 2009
What steps will reproduce the problem?
1. Create a breakpoint on a page and force Firebug to hit it.
2. Try to create a new watch expression while the execution context is
stopped at the breakpoint

The expression input field (within tab watch window) isn't activated when
clicked so.

Test case attached.

1.4 KB   View   Download
Mar 11, 2009
Project Member #1 robmcampbell
(No comment was entered for this change.)
Labels: Type-Defect
Mar 18, 2009
Greetings! I read the workaround posted here:

However, I'm unable to create an expression when breakpoints are not active. The option isn't even available.

Perhaps I'm doing something wrong. Suggestions welcome/appreciated!

Apr 17, 2009
Project Member #3
Didn't we used to have a Fireunit test for this case?
Labels: -script -testCase debugger Test-case-available
Apr 23, 2009
Project Member #4
A test case (script/ issue1575 /issue1575Driver.js) is committed (R2624). It currently
fails for me. If the debugger is stopped at a breakpoint, the "New watch
expression..." edit box doesn't work (the inline editor isn't created at all); if not
stopped at a breakpoint it works.


Apr 23, 2009
Project Member #5
Fixed at R2628 on branches/firebug1.4 for 1.4a21. FBTest passes, thanks!
Status: Commit
Labels: -Test-case-available Test-case-in-suite
Apr 28, 2009
Project Member #6
Please try firebug 1.4a22,
Status: Fixed
May 4, 2011
Just changing label Test-case-in-suite to FBTest-available
Labels: -Test-case-in-suite FBTest-available
Apr 5, 2012
(No comment was entered for this change.)
Sign in to add a comment

Powered by Google Project Hosting