Wendall, If you have not changed your system, you can help us by 0) exit firefox 1) Find your profile directory, 2) Copy extensions.cache, compreg.dat and xpti.dat and save them. 3) Delete those files. 4) Restart Firefox Does Firebug work now?
If yes, then please open a bug report on http://code.google.com/p/fbug/issues/list and attach your files so we can take this up with Firefox team. If no, then the problem is not stale data, but more likely another extension. We just need to figure out which one. Open Firefox > Tools > Error Console : any errors? Otherwise the simple thing is to use Firefox > Tools > Addons to disable half of your other extensions, restart, is Firebug working? then repeat until you find the extension(s) that have an issue. jjb On Jun 16, 12:05 pm, "Wendall Cada (wendall911)" <[email protected]> wrote: > 16a12 does not work at all for me with 3.6.3 on Fedora 13. 16a11, > while a little buggy works quite well. I'm not sure how to provide > debugging. But there isn't a single thing that works, it's completely > fubar. I'm not sure if it's just an upgrading issue, or if it works in > a new profile. I can test, but not sure if this is the proper place > for that. > > Wendall > > On Jun 15, 8:17 am, John J Barton <[email protected]> wrote: > > > On Jun 15, 7:56 am, daniel m <[email protected]> wrote: > > > > The latest alpha (1.6X.0a12) of Firebug seems to be fubar'd for me > > > too. I can't get it to inspect anything. In the bottom statusbar of > > > the window it reports errors but every time I click on it Firebug > > > doesn't open, but increases the error count. If I click on the Firebug > > > icon to activate it or try the hotkey it opens.... but without any > > > functionality. Nothing can be entered in the console. No tree shows up > > > on the HTML tab. I have tried this on various websites. I am using > > > Firefox 3.6.3 on OS X 10.6. Looks like I'll have to switch to the > > > stable build for the time being. > > > Hi Daniel. My guess is that this is not related to the problem below. > > > Unfortunately it is possible that your problems are caused by 1.6a12 > > changes that Nicolas avoided by using a new Firefox profile. > > > It would be very helpful if you can do the following test: > > 1) Verify that you still have the problem. > > 2) exit firefox. > > 3) Find your profile directory, > > 4) delete just one file "compreg.dat". This is a special Firefox file > > that will be recreated when you restart. > > 5) restart: do you still have the problem? > > > jjb > > > > On 15 jun, 01:19, Nicolas Hatier <[email protected]> wrote: > > > > > I first noticed issue #3078 > > > > <http://code.google.com/p/fbug/issues/detail?id=3078> was back in > > > > Firebug 1.6X.0a12 / Firefox 3.6.3 > > > > > The test case should > > > > behttp://getfirebug.com/tests/content/console/3078/issue3078.html-butit > > > > completely fails for another unrelated reason, I get "element is > > > > undefined > > > > (49 out of range 27)" > > > > > Then I saw that new Firebug version was behaving incorrectly in several > > > > other cases, throwing incoherent errors "element is undefined" for code > > > > working perfectly with previous FB versions. > > > > > Is it possible something in the code refactoring went very wrong? > > > > > Didn't create a bug report yet because of the scope of this issue - I > > > > wouldn't know where to begin. > > > > > All tested in a brand new profile containing no extension beside > > > > Firebug. > > > > > NH -- 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.
