Broken console logging and firebug window disappears on page refresh

dan_m2k

unread,

Jul 8, 2009, 9:59:06 AM7/8/09

to Firebug

Hi, I'm running 1.4.0.b5 on FF3.5 on Mac OSX. I'm not wearing a turtle-
neck right now.

Firebug seems f*cked in this release, the most notable bugs are:
* console.log and console.log both don't work - haven't tried
console.error
* when a firebug window's displayed, do a page refresh, the window
disappears, meaning another click. Annoying when debugging/ rapid
prototyping.
* on refresh or hide/show, the selected tab is forgotten.

Not a bug, but an annoyance is the change from 'inspect' text button
to the torch icon. Not great for us long-time users.

Thinking of downgrading to see if I can get some features back. Feels
like I've just installed VISTA.

johnjbarton

unread,

Jul 8, 2009, 10:43:03 AM7/8/09

to Firebug

On Jul 8, 6:59 am, dan_m2k <dan....@gmail.com> wrote:
> Hi, I'm running 1.4.0.b5 on FF3.5 on Mac OSX. I'm not wearing a turtle-
> neck right now.
>
> Firebug seems f*cked in this release, the most notable bugs are:
> * console.log and console.log both don't work - haven't tried
> console.error

These functions are tested in all 1.4b and 1.5a releases.

> * when a firebug window's displayed, do a page refresh, the window
> disappears, meaning another click. Annoying when debugging/ rapid
> prototyping.

I have no idea what you mean.

> * on refresh or hide/show, the selected tab is forgotten.

?

>
> Not a bug, but an annoyance is the change from 'inspect' text button
> to the torch icon. Not great for us long-time users.

Shift-control-C and right-click Inspect Element are both faster than
the button.

>
> Thinking of downgrading to see if I can get some features back. Feels
> like I've just installed VISTA.

My first suggestion is that you create a new Firefox profile. Sounds
like yours is, well, that word you used above.
See http://groups.google.com/group/firebug/web/faq-about-firebug for
hints.

jjb

Saikat Chakrabarti

unread,

Jul 8, 2009, 3:07:42 PM7/8/09

to Firebug

I was having the problem with console.log being undefined when running
1.4.0.b5 and 1.5.0a9 on FF3.5 on Leopard. Just upgraded to 1.5.0a10
and the problem is gone.

chiller

unread,

Jul 8, 2009, 6:01:57 PM7/8/09

to Firebug

I have had the same issue with console.log not displaying anything
from 1.4.0b4 thru 1.5.0a10. I'll try wiping my profile, but that is a
bad workaround.

johnjbarton

unread,

Jul 8, 2009, 6:10:37 PM7/8/09

to Firebug

You can just create a new one, if it does not help, go back to the
first one. Not great, but if something is interfering with Firebug
what can we do.
jjb

Reply all

Reply to author

Forward