I'll just ask you to consider things from our side. We listening for every hint about possible serious bugs. We are waiting for anything close to a test case we can reproduce. I absolutely do not buy any claims that somehow 1.3 is less robust or more buggy than any previous version of Firebug. This is the most tested and carefully worked version yet. We have over a million daily users (https:// addons.mozilla.org/en-US/firefox/statistics/addon/1843). Yes we have some folks with problems and they probably represent others who have not complained. But overall 1.3 is solid. The credit here goes to the Firebug team most especially many users who try our alpha and beta versions, contributing a lot of time and energy to help us find bugs and improve features.
Ok enough with the preaching. Let's see if we can sort out your problem. Assuming that you won't be debugging Firebug on your system, we have to figure out how to transfer your problem to our machines. The first step is to reproduce the problem on your machine using the same software we use. That's why I asked for the new profile. Let's stick with that. Next we need you to be able to reproduce the problem, you seem to have it in the "load a page with a get". Here we have two paths. You can try to re-work your case down to just the essential element that is failing, something that you can post to our bug report. It would be small enough and absent any commercially sensitive or private code. This can be difficult I know. Or we can try to get tracing information. Here's how to do that: Install Firebug 1.3X.3 from http://getfirebug.com/releases/firebug/1.3X. Get your test case loaded but don't push the reload-get yet. Open firebug and use the Firebug icon menu to Open Firebug Tracing. In the Options tab select ERRORS and SOURCEFILES push the reload-get At the top of the trace window, Save to File. Attach that to an issue (bug report) http://code.google.com/p/fbug/issues/list Its possible that the ERRORS setting will tell us something right off if we get lucky. Else this may take a few rounds and some patience. jjb On Feb 24, 7:36 pm, otie <[email protected]> wrote: > sounds good. except when I loaded the page with a get, the javascript > stopped functioning. when I got rid of the get, it worked. Certainly, > the code may be broken. But it was strangely consistent. > > Bottom line, there is a condition where firebug loses the javascript. > The get may or may not be the cause. I realize it makes no sense. But > surely you've experienced an apparent cause to a problem actually > masking something else. > > The number of people experiencing problems suggests there's some truly > elegant bug. (I always try to make stupid mistakes because they're > easier to find.) > > I've been using firebug for more than a year now, constantly. It's > been the tool that's allowed me to write neat pages which work and > advance the cause of intuitive user interface. Since 1.3 it's been, > although more elegant, less solid. For instance, if firebug found an > error in the load check chain, it would freeze firefox necessitating a > 'force quit' (I'm on a mac). > > I see other comments with problems similar to mine. > > I assert that somewhere in firebug (perhaps in firefox as well, given > the complaints), there are elegant, innocuous bits of code -- a sem- > colon, an = instead of an ==, you know the drill, bits none of us are > immune from. > > Firebug is arguably the best debugger I've ever used. No question. > Otherwise, I'd be ignoring this and finding something else. It's > interesting that with all the activity in the web world, there's only > one serious debugging tool. Maybe this says that all the other coders > are geniuses. I am not one, so I depend on firebug. > > Perhaps I could use the tracing version to find what's happening. I'm > sure that any instance where firebug suddenly can't recognize > javascript raises questions. To say my installation is flawed, > although possibly true, suggests firebug is ... delicate. Not a > compliment for any software. > > I'm at your service in whatever respect I can contribute. I await your > suggestions. > > Thanks, > > O. > > Otis Maclay > Houston > > On Feb 24, 7:32 pm, John J Barton <[email protected]> wrote: > > > I'm not following you. What does it mean to reload with GET? You > > mean you loaded a URL that happened to be the same as the page having > > the link? So its not really a reload but a load? Anyway these pages, > > before the load and after the load are not connected by Firebug or > > Firefox, except that breakpoint URLs are remembered. So the js that > > does not work just does not work, it was not working 'before' because > > the new page has nothing to do with the old one. Loading total > > flushes out the page and a new one is created. > > > jjb > > > On Feb 24, 4:40 pm, otie <[email protected]> wrote: > > > > how about this... > > > > i was reloading using an old menu item with a GET (?log=upload) which > > > wasn't used. If I reloaded without the get, it was ok, but with the > > > get, firebug wouldn't see the js (the line numbers greyed out), and > > > the js on the page which was working stopped... > > > > I can't test it on getfirebug.com because of the redirect > > > > I've tested it in some other places.. not consistent. > > > > But it does seem to be consistent with the page I was having the > > > problem with. > > > > ??? > > > !!! > > > > O. > > > > On Feb 24, 5:57 pm, John J Barton <[email protected]> wrote: > > > > > On Feb 24, 3:42 pm, otie <[email protected]> wrote: > > > > > > well.... > > > > > > I created a new profile and reinstalled firebug. > > > > > > same problem Not only does firebug not see js, firefox doesn't either. > > > > > We need to work from this state, that is just after you have created a > > > > new firefox profile and added only firebug. > > > > > In that state do you see js on other sites, sayhttp://getfirebug.com? > > > > > Ok, good. > > > > > Now try your site. if you don't see the js we need know what is > > > > different about your site. If you can't figure that out or can't > > > > share about it, you can try the tracing version of Firebug. Let me > > > > know I'll give you the instructions. > > > > > If you just want to give up, you can install any previous version of > > > > Firebug. But of course we can't help you with bugs there. > > > > > jjb > > > > > jjb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
