On Jul 28, 11:20 am, Prefontim <[email protected]> wrote: > It's our own company's app, call webNetwork. It's basically a virtual > web desktop, and contains dozens of apps inside it. There are public > versions of it available, which could be used for debugging. However, > most of the bugs i mentioned happen while i am changing code, which > can't as easily be done on a public site. > > I have searched Bugzilla and came up some ticktets that may be related > to my issues: > > 1. 2028 > 3. 2948 > 5. 2647
None of these issues have a test case. I can't reproduce the problem so how can I fix it? > > Anways, to follow up on my previous comments, my feeling is that the > issues i face is probably common to anyone who uses a complicated app, > because i have them so easliy. If the Firebug developers had some > kind of 'master complicated app', (e.g. - similar to google mail) > simple test cases would become obsolete as this app could be used to > duplicate all of the above issues. We don't have any such application, so we can't duplicate any of those issues. If you were to provide such an application that duplicated the above issues, then we could fix them. One approach that I have used successfully in the past is for users to run with Firebug tracing and post the traces to the issues list. jjb > > On Jul 28, 1:55 pm, John J Barton <[email protected]> wrote: > > > On Jul 28, 10:21 am, Prefontim <[email protected]> wrote: > > > > I have posted over 10 tickets to the Bugzilla system with much success > > > at getting resolution as i don't post anymore unless i have a test > > > case. However, all of the most serious bugs I face on a daily basis i > > > can't get resolution for because i can't come up with a test case. > > > With most of issues, i am debugging my fairly complicated webapps and > > > then things just stop working. It is impossible to know exactly what > > > caused it, so a test case is hard to make. > > > > For a complicated app, my companies apps all have many iframes. Most > > > iframes have dojo in them, and dozens of other scripts. There are > > > many dom transformations and xhr requests happening all the time. > > > WHen things go wrong with these kinds of apps, it is hard to simulate > > > issues with simple test cases. It's hard just to reproduce them, in > > > general, as i don't noticed things are broken until i need them. > > > > So, i thought i'd list all these bugs that i encounter on a daily > > > basis. Most of them have been happening to me since I started using > > > Firebug (1.2 or 1.3). What i am hoping is that maybe the Firebug > > > developers could take the opposite approach with these bugs. Instead > > > of requiring a simple test case, maybe they could test against a > > > complicated app until they can reproduce some of them. If not, maybe > > > others will post to this with experiences with these bugs. > > > Which complicated app? It's not like I can see your screen from here. > > > I'll give you the opposite story of frustration from my side: dojo > > users complain about firebug problems but rarely report bugs with test > > cases. There are 4 bug reports related to dojo, none with test > > cases:http://code.google.com/p/fbug/issues/list?can=2&q=dojo > > > > 1. 'console is not defined' - this will start happening at random > > > times. browser must be restarted > > > 2. 'net panel stops working' - net panel will stop showing any > > > requests - browser must be restarted > > > 3. console stops working - console stops showing any logging > > > 4. script panel is empty - script panel will not have a script list - > > > browser must be restarted > > > 5. clicking line number does not add breakpoint - you click on a line > > > number and it does not look like it added a breakpoint, even though it > > > does. the breakpoint shows up only after you click the Watch tab > > > 6. lockup - browser locks up and gets unresponse script errors inside > > > firebugs code. must do force shutdown on browser. > > > I don't know about any reports for the first 6 items. > > > > 7. console shows errors from non-activated pages in other tabs. - for > > > example, i might have Hotmail opened in a different tab, and i will > > > any errors from it in my tab. > > > This particular one is well known to me. 1.6b1 will have another fix > > for this problem, but it's all hacks because Firefox does not support > > this feature directly. > > > 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.
