Fwd: [Mozilla Hacks - the Web developer blog] New Comment On: Firebug 1.10 New Features

[Ken Amron]

---------- Forwarded message ----------
From: Ken Amron <kam...@digital-parts.com>
Date: Sun, Aug 5, 2012 at 6:37 AM
Subject: Re: [Mozilla Hacks - the Web developer blog] New Comment On: Firebug 1.10 New Features
To: "hack.mozilla.org" <nor...@mozilla.org>


I have experienced something similar and as soon as I have time I will attempt to create a minimal test-case for posting the bug I have experienced. I am not certain that it is precisely the same as what you are experiencing, but on the surface it demonstrates many of the same characteristics you describe. 

However, in the meantime,  I have found a workaround which may also be applicable also in your case.

When I have experienced the inability to set breakpoints, I have also experienced the inability to use the "script-selection" tab, just below the main menu. This occurs when the main-menu "Script" tag is selected or attempted to be selected. See attachment (FirebugOutToLunch.png).

Fortunately, when this occurs, the "Console" tab is still workable. You can work around the problem with the following method:

1. In the module you want to breakpoint, use console.debug() to place a log message into the console.

2. When you gain control in Firebug, select the "Console" tab and then use the log entry that you have created to navigate to the module of interest -- in the example attached, you would navigate by selecting "qTreeDisplay.js (line 402). 

3. Firebug then transitions you, by default selecting the "Script" tab, with the "script-selection" drop down, pre-selected to the javascript module of interest. 

I have been able to work around the problem you described with this method.

On Sat, Aug 4, 2012 at 5:56 AM, hack.mozilla.org <nor...@mozilla.org> wrote:

There is a new comment on the post "Firebug 1.10 New Features".
https://hacks.mozilla.org/2012/07/firebug-1-10-new-features/

Author: Ian
Comment:
Since a forced update to firebug 1.10... I'm unable to set breakpoints at all!?  All javascript code-lines are greyed out and breakpoints are "undefined" with a "out of range"  WTH, ?? I can't do any work.

See all comments on this post here:
https://hacks.mozilla.org/2012/07/firebug-1-10-new-features/#comments

To manage your subscriptions or to block all notifications from this site, click the link below:
https://hacks.mozilla.org/?wp-subscription-manager=1&email=kamron%40digital-parts.com&key=3ddec67af2fea4e6e63186994d261694

--
Ken Amron
Digital Parts, Inc.
877.374.4300 ext. 567

--
Ken Amron
Digital Parts, Inc.
877.374.4300 ext. 567

[Sebastian Zartner]

The UI problem shown in FirebugOutToLunch.png is obviously a Firefox bug. Please turn off hardware acceleration (see the other thread how to do that)  and let us know if that fixes the problem.

Sebastian