Hi John, my apologies if my original post came across as whining or as a rant. 'Certainly didn't intend it to be such. Rather, there was just a general sense among my team here with how unreliable has been for us Firebug was for our team and I wanted to see what suggestions this community might have to help address the problem.
As you guessed, the 1.3.3b3 release proved to be of little help. However, the suggestion of testing with a new profile was certainly useful. With it we were able to isolate at least one of the problem as being related to having the Web Developer addon installed. I've filed a bug report here: http://code.google.com/p/fbug/issues/detail?id=1504 ... which brings me to another question. I certainly appreciate how useful concrete bug reports are but can you comment on whether or not a report like the one above is actually useful to you? I was unable to isolate the problem to a standalone test case and, instead, am forced to provide a recipe that just referes to a page on our website. Unfortunately I can't make any guarantees as to how long that page will be useful as a resource in reproducing this bug, which has me wondering if I should have even bothered... :-P (That said, this is a "Firefox crasher" bug, so I'm hoping it'll get some attention ASAP. :) ) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
