You need to overlay firebugOverlay.xul in your chrome.manifest file: overlay chrome://firebug/content/firebugOverlay.xul chrome://cssUpdater/content/ff-overlay.xul
(not browser.xul) When I change that the extension seems to be working again. Honza On Sep 30, 10:56 pm, Johan Andersson <[email protected]> wrote: > Thank you for answering! > > But I can't see anything special with your example that I isn't doing. > The only diff I see is that I use ActivablePanel and module. > > So when I add this fail safe debug logic (without anything in the middle) > > alert("first line"); > FBL.ns(function() { with (FBL) { > alert("middle line");}}); > > alert("last line"); > > Then the first and last line is alerted. It does not even try to execute > the thing in between for me. > Using FireBug 1.9.0a3, FireFox 6.0.2 > > On Sep 29, 2011, at 3:47 PM, Jan Honza Odvarko wrote: > > > > > > > > > Take a look at this HelloWorld example: > >http://code.google.com/p/fbug/source/browse/#svn%2Fexamples%2Ffirebug... > > > It works for me in Firebug 1.8 and 1.9 > > > It also uses the same boilerplate: > > > FBL.ns(function() { with (FBL) { > > > Honza > > > On Sep 27, 7:53 pm, Jhonte <[email protected]> wrote: > >> Thank you for trying to help Nero :) > > >> The global variables is check, how ever it seems like this code: > >> FBL.ns(function() { with (FBL) { > > >> Should be something totally different in 1.9? Where can I find > >> documentation about this change, (and how can I make it work with > >> FireBug < 1.9) > > >> On Sep 27, 12:02 pm, Jan Honza Odvarko <[email protected]> wrote: > > >>> On Sep 26, 5:28 pm, Nero <[email protected]> wrote:> Errors is the only > >>> one that I have checked and still nothing showed up. Am > >>>> I to assume that in this case it's the extension itself that needs fixing > >>>> and nothing something in Firebug? > > >>> The Firefox Error console also doesn't show any error/exception? > > >>>> Is there any info I can forward along to the developer? > > >>> The most important info for a developer is usually a test case > >>> + detailed steps how to reproduce the problem. > > >>> I don't know how long the extension wasn't updated, but > >>> sometime along Firebug 1.7 release we removed two global > >>> variables: > > >>> FirebugContext -> is now -> Firebug.currentContext > >>> FirebugChrome -> is now -> Firebug.chrome > > >>> You could also mention this to the developer > >>> Honza > > > -- > > You received this message because you are subscribed to the Google Groups > > "Firebug" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/firebug?hl=en. -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
