Firebug not reactivating after a restart

198 views
Skip to first unread message

Nicolas Hatier

unread,
Oct 18, 2012, 2:36:13 PM10/18/12
to @Group: Firebug
What could cause Firebug NOT reactivating on a firebugged page when
Firefox is restarted?

- I used "Reset All Firebug Options" and the "Clear Activation List" menus
- I made sure "Activate For Same Origin URLs" is enabled
- I opened getfirebug.com
- I opened Firebug
- annotations.json now contains
[{"uri":"https://getfirebug.com/","value":"firebugged.showFirebug"}]
- I restarted Firefox
- Firebug didn't open, but annotation.json still contains the same data.

Firebug stays open when I refresh the page, or if I close the tab and
open a new one with the same URL. The problem is just with full close of
Firefox.

Is it just me?

Fails on 1.10.4, 1.11.0a4
Works (no problem) with 1.9.2, though.

On Firefox 15.0.1 and 16.0.1

I can file a bug once someone tells me I'm not that crazy :-)

Nicolas

Sebastian Zartner

unread,
Oct 18, 2012, 6:02:58 PM10/18/12
to fir...@googlegroups.com
It's not a bug, it's a feature. :-)
Firebug is now delayed loaded to avoid slowing down the browser start. This means it isn't loaded until you press F12 or click the Start Button.
This behavior can be switched back to the old one again with some restrictions by setting extensions.firebug.delayLoad to false.

Sebastian

Nicolas Hatier

unread,
Oct 20, 2012, 12:20:23 AM10/20/12
to fir...@googlegroups.com
Thanks.

The issue 5623 seem to imply everything is fixed regarding this. However, when I restart Firefox, Firebug's debugger and console are activated only after the page is loaded, not before, so any initialisation breakpoint isn't reached, and any initialisation logging doesn't display.

(Using 1.11.0a5)

But I'm sure I can live with that.

Nicolas

Sebastian Zartner

unread,
Oct 20, 2012, 7:59:51 AM10/20/12
to fir...@googlegroups.com
The issue 5623 seem to imply everything is fixed regarding this. However, when I restart Firefox, Firebug's debugger and console are activated only after the page is loaded, not before, so any initialisation breakpoint isn't reached, and any initialisation logging doesn't display.
In the issue and in my previous post it's already mentioned that it's not completely working as before yet. Therefore I created issue 6015 now.

Sebastian
Reply all
Reply to author
Forward
0 new messages