Firebug 2.0.4

[Sebastian Zartner]

https://blog.getfirebug.com/2014/09/06/firebug-2-0-4/

Sebastian

[Jason Chantrelle]

Greetings,

I hope this is the correct forum for reporting what may be a bug.

Firefox automatically updated to version 32.0.2 last night (I know, I know, disable automatic updates, I know) on my 2008/9 17" MacBook Pro running OS X 10.9.4.
I had been using Firebug 1.something with no problems. Then I noticed my console.logs weren't looking right this afternoon, objects weren't being displayed properly, etc.
This is when I became aware of the browser update. I then updated Firebug to 2.0.4. Console.logs looked normal again, Great right!!
Not quite, when I click on a post comma console.logged object expecting to be shown its innards in DOM view, alas, DOM tab is activate but the console view remains.
This is NOT good!

What do I do here? Wait for the next upgrade?

On Saturday, September 6, 2014 1:10:52 PM UTC-4, Sebastian Zartner wrote:

https://blog.getfirebug.com/2014/09/06/firebug-2-0-4/

Sebastian

[jerone]

Firebug 2.0.4b1 has also been released to update users on AMO beta channel.

Three weeks later and still no 2.0.4b1, latest beta version 2.0.3b1 on AMO. Version not approved?
 

[Jan Honza Odvarko]

On Thursday, September 25, 2014 11:25:32 AM UTC+2, jerone wrote:

Firebug 2.0.4b1 has also been released to update users on AMO beta channel.

Three weeks later and still no 2.0.4b1, latest beta version 2.0.3b1 on AMO. Version not approved?

Sorry, there is currently a problem on AMO and I can't upload those.
In any case you can use XPIs from getfirebug.com
https://getfirebug.com/releases/firebug/2.0/
(they are exactly the same and you'll stay on the AMO beta channel)

Honza
 

[Jan Honza Odvarko]

AMO updated now

Honza

[Brian]

Hello,

I hope this is the place to report bugs and issues for Firebug...

I'm still having issues with this release of Firebug and FF 32.0.3. When I'm not using firebug, FF works normally with no issues and uses less than 500mb of ram for 7 tabs. When I use Firebug to inspect an element, view the console, etc., FF begins to use a ton of ram almost 2GBs for 7 tabs! Then FF begins to not respond periodically and becomes very slow.  The way I have been working around this is to use firebug when I absolutely have to and then restart FF after I'm done to free up ram and have a speedy FF.

Thanks,
Brian

[Sebastian Zartner]

Can you break that down to a simple test case with steps to reproduce? You may also analyze the memory usage via about:memory.

Sebastian

[Ales Seifert]

jQuery Validation plugin is not working when FireBug is enabled, look here: http://jqueryvalidation.org/files/demo/

FF 33.0, FB 2.0.4b1

[Andrea Mauro]

Older versions of JqueryUI don't work anymore with the last version of firebug/firefox (FF 33.0, FB 2.0.4). They were working properly a couple of weeks ago, before the FF33 update I suppose.

To reproduce the bug, download the jqueryUI 1.9.x full package from the official site and open the included index.html.
http://jqueryui.com/download/#!version=1.9.2
Enabling firebug breaks entirely the interactivity with any JqueryUI element.

On my intranet webapp I can see this error appear whenever I try to open a JqueryUI datepicker with firebug activated:
uncaught exception: Missing instance data for this datepicker


I detected other anomalies with other plugins like jqgrid and ajax-chosen

[Andrea Mauro]

I posted a bug report, is this thread moderated?

[Jan Honza Odvarko]

Yes, the first message always goes through moderation. You've been approved
and your next messages will appear automatically.

Honza

[Bibendus@Gmail]

Thanks, I didn't notice the small yellow message on the bottome of the page.
I noticed it the second time ;)

Bibendus

--
You received this message because you are subscribed to a topic in the Google Groups "Firebug" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebug/JT6QYNfsVow/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebug+u...@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at http://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/b452d05b-3f6a-4a74-8393-8ec297b0bcd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Isidro Moran]

The new Firefox updates messed up with Firebug.  Javascript stops working on the sites if you enable it.  I have to downgrade to version 32. 

[Ales Seifert]

Problem was caused by FireQuery 1.4.1 plugin

[Andrea Mauro]

Confirmed!
Thanks Ales