Wednesday, January 20th, 2010

Firebug 1.5: New Features and ready for Firefox 3.6

Category: Debugging, Firefox

>Nice work Firebug team for announcing Firebug 1.5, a great release that fixes many bugs and adds great features:

  • Mike Radcliffe’s Inspector. A key feature, now solid as a rock,
  • Jan ‘Honza’ Odvarko’s expanded and refined Net panel, with accurate timings,
  • Steve Roussey’s reworking of HTML editing and entity support,
  • Kevin Decker’s CSS and Style side panel improvements,
  • Support for dynamic, graphical breakpoints through out Firebug.
  • Tested support for the soon-to-be-released Firefox 3.6

This is a big deal. The release is out *before* Firefox 3.6. No more “oh man we have a new Firefox but it doesn’t work with Firebug argh”. Awesome.

Related Content:

Posted by Dion Almaer at 6:49 am
28 Comments

++++-
4.6 rating from 61 votes

28 Comments »

Comments feed TrackBack URI

It repeatedly crashes my Firefox 3.5.6 when I try to inspect element from context menu or just open up firebug window by clicking grey bug in status bar. Thats improvement there for sure, since I can’t see any other bugs now.
The only other extensions I have is greasemonkey, Adblock+ and Adblock+ Element Hiding Helper.

Comment by paziek — January 20, 2010

not working for me either in FF 3.5.7. Its not crashing but inspecting elements is not working, browsing my site in “HTML”-Tab ist not working. What kind of a release is it? a Beta version for the users to test?
I have to downgrade somehow

Comment by StilgarBF — January 20, 2010

It’s functioning for me in FF 3.6 RC. But…

Where the hell is the most useful option in the “Script” tab? BREAK ON ALL ERRORS!!!

Comment by ExtAnimal — January 20, 2010

fireQuery needs to be updated if you use it
see http://blog.getfirebug.com/2010/01/19/please-update-firebug-extensions-with-1-5-0/
with fireQuery 4.1 my firebug 1.5 works ok. – sorry for the fuss

Comment by StilgarBF — January 20, 2010

@paziek & @stilgarBF is there an example page where this is crashing for you? We’ve been testing on 3.5 as well as 3.6 and haven’t seen inspector bugs, especially crashers. Which operating system are you using?

@ExtAnimal Break on Errors has been moved to the Console tab’s “Pause” button.

Comment by robcee — January 20, 2010

@robcee: Its on Ubuntu 9.10 (run on Windows 7 via VirtualBox)
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.6) Gecko/20091215 Ubuntu/9.10 (karmic) Firefox/3.5.6

Also, I installed Firebug 1.4.5 again and it worked. So I installed 1.5 one more time, closed all tabs, removed all extension, went to about:blank and still crash.

Comment by paziek — January 20, 2010

Took it for a test drive. Looks like a solid release. A bit faster, which is more than welcome (every inspector in every browser is slow when dealing with extjs). Good job from the firebug devs.

I did notice one little issue. Clickthrough from the console’s error reporting seems to not be accurate. I had two errors, and clicking the first took me to the place in the source of the second error (the first was an unclosed string literal that indirectly caused the second error, which was a missing function). The error’s line number reported in each case was correct though.

Comment by Joeri — January 20, 2010

OK, I found it, thanks @robcee.

But that’s an absolutely bizarre place for it! Why *remove* the option from the “Script” tab in the first place?

Comment by ExtAnimal — January 20, 2010

Sorry – FireBug,

but FireBug fires bugs all the times.

– set of CSS attributes doesn’t work
– unable to set break points. Must reload the JS 2 or 3 times
– crashing during debug
– prototype AJAX misbehaviour (onComplete not called sometimes)

sorry – Firebug for FireFox 2.x is greate but horrible for >3.5

Andreas

Comment by 65r5z6 — January 20, 2010

And yet the “The value is meaningless” bug persists (at least with FF 3.5.7, FB 1.5 and ExtJS 3.1) on any form field.

“The ‘charCode’ property of a [keydown/keyup] event should not be used. The value is meaningless.”

Comment by httpdotcom — January 20, 2010

I have upgraded my firefox to: Mozilla/5.0 (X11; U; Linux x86_64; pl-PL; rv:1.9.1.7) Gecko/20100106 Ubuntu/9.10 (karmic) Firefox/3.5.7
And it still crashed when I try to bring up firebug window.

Comment by paziek — January 20, 2010

@paziek

you must downgrade to Firefox 2.9 and Firebug 1.0 for a stable system.

Comment by 65r5z6 — January 20, 2010

I’ve been using Firebug 1.5 on Fx 3.6 this morning, and it’s working well.

Comment by WillPeavy — January 20, 2010

I’ve just had the debugger jump to completely the wrong line of ext-all-debug.js. Firebug really does get horribly confused if the source file you are debugging is 70,000 lines long.

Comment by ExtAnimal — January 20, 2010

Ubuntu 9.10, click the grey bug icon => instant crash

Comment by nasp — January 20, 2010

I think you should pull this version from stable label, as this clearly isn’t stable yet. Seems like I’m not the only one with the issues.

Comment by paziek — January 20, 2010

Yeah, installed it, uninstalled it and re-installed 1.4, all good again.

My FF didn’t crash but I saw problems with scripts not being shown as present, breakpoints could not be set (easily) and the lack of the “Break on all errors” option nearly gave me a coronary!!

Looking forward to the unofficially ‘stable’ release

Comment by RoryH — January 20, 2010

New firebug is still buggy, sometimes don’t show errors. It’s suxx. If i
have typo conosle.log firebug don’t show it very often. Only after
opening page in new tab or new window firebug begin to show errors.

Firebug developers – stop creating new features and changes how it’s work, make it free of bugs before!

my environment – ff3.5.7 mac os x 10.5.8 firebug 1.5

Comment by magmoro — January 20, 2010

I’m a big ExtJS user (stever on the forums — wish I could change my name there), and joined the Firebug Working Group last year to focus on fixing bugs. Like all devs know, a solid and simple test case is the key to fixing stuff. And you the issue list is here:
http://code.google.com/p/fbug/issues/

Create a new one here:
http://code.google.com/p/fbug/issues/entry

I can’t say I added much as far as features, but I was nicknamed a ‘serial bug killer’. ;) That said, I’m making a Firebug extension for all you JS framework users (jQuery, ExtJS, etc) for the 1.6 time frame. I’m going to succumb to feature bloat, but it will be a separate extension.

A few notes on problems installing Firebug 1.5:
- If you are running Ubuntu 64bit, they ship a buggy version of Firefox in 64bit that will crash. Suse has the bugfix backported from 3.6, I believe, so they are in the clear. Ubuntu 64bit users should download something from Mozilla directly (either 32bit 3.5 or either 32/64 of Fx 3.6) or complain to Ubuntu.

- If you have firebug extensions (FireDiff, FirePHP, FireQuery, etc.), they need to be updated at the same time! A goal for Firebug 1.6 is to get the extension makers on board and have them tested as a group.

- If the install of Firebug fails, try with anti-virus off. There is an anti-virus company that gets tripped up by Firebug installing for God knows what reason, but it makes a mess of things.

Comment by sroussey — January 20, 2010

Thanks Firebug team.
I do appreciate all the work you guys are doing.

While I have not yet tested (have to restart the browser), I have no lack of thanks for your work at making my job doable.

Comment by SamGoody — January 20, 2010

I really appreciate Firebug, I use it constantly to do my work, and appreciate those that work on it.

Unfortunately I have to concur with other Ubuntu users that this latest release only makes my Firefox browser crash when I go to inspect. I’ll have to downgrade, and update once it gets the kinks worked out.

Comment by sarahp — January 20, 2010

Will be great when its finished but right now I’d be happy if I could get it to stop at just one breakpoint :-(

Comment by AngusC — January 20, 2010

For those with using firefox on 64-bit linux. There is a bug in firefox (fixed in 3.5.8 or 3.6) that is causing a crash with firebug 1.5. Probably should have waited to release it, but i am having good luck with it in 3.6 RC1.

Comment by datasage — January 21, 2010

The “Break on all errors” option now breaks on WARNINGS!

This is not good and makes debugging ERRORS quite difficult when you have to continue over scores of warnings!

Comment by ExtAnimal — January 21, 2010

Tried 1.5, reverted back to 1.4.5

First 2 things (essential) that do not work:
1) Break on all errors does not break at all
2) Clicking on the link (line …) in Console tab, does not open the file (it switches to the Script tab but the panel is blank)

Comment by fermo111 — January 21, 2010

Firebug 1.5.0 is not crashing FF 3.6pre when I inspect DOM elements on my Ubuntu 9.04 64bit. Maybe I’m just lucky but according to datasage the browser shouldn’t crash with this version of FF.

Comment by pmontrasio — January 21, 2010

Thats very helpful thanks you

Comment by Aphrodisiac — January 22, 2010

A positive comment: I’m loving this new release, works better and faster. Keep up the great work and add more features too.

Comment by jerone — January 22, 2010

Leave a comment

You must be logged in to post a comment.