Firebut 1.10 support for debugging extensions?

[Ben]

Hey guys, great work on an excellent plug-in. Been relying on it for years. 

Am I right to understand that with 1.10 I can no longer step through scripts loaded via the chrome? Since the demise of chromebug, I've limped by with FF5 and last version of chromebug, and in other cases loaded the chrome window directly in the browser bar and used the current Firebug to step through code and debug. 

I got the message after updating that Firebug can't show scripts for internal sources (don't have the error in front of me,  reverted to 1.9.2);

As FB Trace doesn't seem to offer step-through support, what do you guys use to debug Firebug as you write it? I feel like I'm missing something (I've looked at the "working chromebug / firebug / XULRunner combination" post, but it says basically that there is nothing that can step through code. Can it be that there is not one robust step-through and DOM inspection tool for authoring Firefox Extensions in the whole FF Extension ecosystem? 

I would say I'm still a beginning / intermediate FF extension developer - so maybe I've missed the proper IDE that folks develop extensions in.

thanks again guys, 

Ben 

[Jan Honza Odvarko]

On Jul 17, 3:34 am, Ben <ben.will...@gmail.com> wrote:
> As FB Trace doesn't seem to offer step-through support, what do you guys
> use to debug Firebug as you write it? I feel like I'm missing something

For me FBTrace is the main tool helping me debug Firebug.
https://getfirebug.com/wiki/index.php/FBTrace

Honza

[Sebastian Zartner]

For me FBTrace is the main tool helping me debug Firebug.
https://getfirebug.com/wiki/index.php/FBTrace

It doesn't offer step-debugging through the code but gives you all the information you need when setting FBTrace logs at the right positions. For inspecting the chrome sources I use DOM Inspector.

Sebastian

[Ben]

Thanks guys, I'll give these a shot. 

Best 

Ben 

[TheRave]

It was not an good idea to kick chromebug. Instead Firebug we can use the Fx internal debugger now and for chrome debugging we have nothing. I see lots of reasons for chromebug and only one reason for firebug. ---> Chromebug.

[Jan Honza Odvarko]

See this: http://blog.astithas.com/2012/10/debugging-firefox.html
Honza