I think that people should not expect resolution unless they attach a test case or trace. However, it can still be a good idea to post issues without those things, in the hopes that they or others will have steps to duplicate.
But, regardless, the point of this post was not to say that any bug ticket should get fixed, even ones without test cases. Instead, it was to suggest an alternate way of generating bug tickets. One which would be a supplement to the issue-finding process, and could be a good way to find issues that affect complicated apps, like mine. But, i do very much appreciate all the contributors efforts, and would not want to place any extra burden on them, unless they chose it that way. The best counter-suggestion was to use the trace logs, which I subsequently did in the following ticket, to much success: http://code.google.com/p/fbug/issues/detail?id=3292 So, i will continue to use trace logs to figure out the remainder of my complicated issues. On Jul 31, 2:42 am, Garrett Smith <[email protected]> wrote: > On 7/30/10, John J Barton <[email protected]> wrote: > > > > > > > On Jul 30, 10:00 am, Garrett Smith <[email protected]> wrote: > >> On 7/29/10, John J Barton <[email protected]> wrote: > > >> > On Jul 29, 5:39 am, Prefontim <[email protected]> wrote: > >> >> I would agree with the general tenor of these responses, in that > >> >> complicated apps are not as good for automation or for tracking down > >> >> issues once they are found. However, they are much better than simple > >> >> tests at actually discovering issues in the first place. If a > >> >> complicated app was constructed by the Firebug team, and they simply > >> >> just used the app for 15 minutes, they would probably discover > >> >> multiple issues. Since they made the app, they would be in a position > >> >> to debug it effectively. > > >> > We already do this. We use the Firebug code to debug a complex 40kloc > >> > application using a wide spectrum of Web and XUL technologies. Rather > >> > than 15 minutes, we use it all day every day. And yes it has allowed > >> > us to discover many issues in Firebug code. (The application is called > >> > "firebug" in case you are interested ;-). > > >> > I think that your analysis is missing three important aspects related > >> > to the scale of these issues. > > >> > First, while you imagine that 'everyone' has the problems you have, it > >> > just cannot be true. With 2.6 million users, only a tiny fraction > >> > report problems. > > >> OK, but don't expect a lack of reports for a lack of errors. > > >> Sometimes it is necessary to restart Firefox to get Firebug working. > >> SOmetimes just opening a new tab works and that is easier, so I > >> usually try that first. I have experienced all of the OP's 7 items, so > >> that's how I know. > > >> I'm sorry I can't be of more help. I don't know what triggers the > >> problems and so I haven't been able to file a proper bug report. > > > A good place to start is > > 1. Open firebug tracing panel with option ERRORS > > 2. The first time you have a problem, check the trace. > > 3. Whether or not there is any info in the trace, describe exactly > > what the problem is. 'net panel stops working' is not enough. Is it > > blank? is the Console panel still showing XHR? If you set NET on the > > tracing options do you see stuff? > > >> Maybe the someone has time can take one bug and investigate it and > >> hopefully provide more detail (steps to repro, etc). > > > Only you two with the problem c > > No, not only us two; the OP is bringing up bugs that others have > reported. Looking at the bugtracker: > 2948: Console stops working (No XHR or log outputs) > > With comment from " lisman.aaron, Apr 12, 2010" and " gullevek, Jun > 17, 2010" confirming the same. > > http://code.google.com/p/fbug/issues/detail?id=2948&q=console%20stops... > > I have other issues at the moment and a ton of stuff on my plate. > Sorry, there are real issues. They don't bug me enough to motivate me > to investigate further. I'm just busy with a bunch of stuff. Thanks. -- 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.
