Recent Firebug Google Groups posts

Re: console (ie: console.log, console.debug, etc) output quit working with update from Monday, July 28th, 2014 on Firefox 33.0a2 (2014-07-30)

Thanks for the hint. We are aware of that and already have a fix, which will be released with the next version of Firebug. See issue 7597 for more info. Sebastian On Wednesday, July 30, 2014 9:26:29 PM UTC+2, squidly2112 wrote: > > Throws error... Continued on Google Groups »

console (ie: console.log, console.debug, etc) output quit working with update from Monday, July 28th, 2014 on Firefox 33.0a2 (2014-07-30)

Throws error that "debug" is not a function when trying to execute console.debug(), or any other console function. ¬†Everything has worked swell up until the Monday, July 28th, 2014 automatic update.... Continued on Google Groups »

Re: Firebug looks ugly with the Nasa Night Launch Theme

We were already in contact with mcdavis, the author of NASA Night Launch, before the release of Firebug 2.0. Unfortunately he was busy with the adjustments for Australis (the new Firefox UI) at that time. I CC'ed him on this message, so maybe he can give feedback on this. Sebastian On Wednesday, Jul... Continued on Google Groups »

Firebug looks ugly with the Nasa Night Launch Theme

the tab bar looks plain weird, with the dark theme, but I like dark version of everything so please if anyone can help me out.... Continued on Google Groups »

firebug hover option

in firebug 2.2.0 ¬†hover option not working , wheb I am googing to style tab and hover option it`s not working. I am using ff 31.0. Plz fix this issues. P;z check this - http://prntscr.com/47hs7j... Continued on Google Groups »

Re: v2.02 trace.js:55 stopped responding

I am having the same problems. Running a project on my local machine, Windows 7, in the last week, suddenly getting this error all over the place. Using Firefox 30.0 and firebug 2.0.2. Script keeps hanging and giving this message: chrome://firebug/content/lib/trace.js:55 I don't know how to downgrad... Continued on Google Groups »

Re: v2.02 trace.js:55 stopped responding

I am, since the last update of Firefox (31.0). With some internal projects with MooTools code, we all get blocking errors as mentioned above, especially using mootools.min. But even with http://google.com, the whole browser blocks for 1-2 seconds before rendering the page.... Continued on Google Groups »

Re: v2.02 trace.js:55 stopped responding

OK, thanks for the update! Honza... Continued on Google Groups »

Re: v2.02 trace.js:55 stopped responding

For what it's worth, I downgrade to firebug-1.12.8b1.xpi, then reinstalled firebug-2.0b8.xpi and it seems to have solved the problem. Sorry I couldn't give any more information...... Continued on Google Groups »

Re: v2.02 trace.js:55 stopped responding

Sorry, they're only available on an internal network. I realize this makes it impossible to reproduce... I was just wondering if anyone else was experiencing this. On Monday, July 21, 2014 12:10:42 PM UTC-6, Jan Honza Odvarko wrote: > > What exactly are you doing? > > Any chance to access your page... Continued on Google Groups »

Read more on Firebug Google Groups »