Sent from my iPhone
On Jul 28, 2010, at 2:20 PM, 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. > ... Between a person who sees a problem and a person who does not, who is better positioned to document it? The person who sees it has a context, which while perhaps large, is a great deal more specific than the universe if possibilities the FB developers would have to explore. An observation on this general class of issues: perhaps it is inaccurate, but my sense in watching this forum, and others, is that quite frequently these difficult problems end up tracing back to something like an obscure error in the user's code or logic. Often a simple typo. The difficulty is basically in the way those often manifest themselves. Often is is very obscure, giving little clue to the true nature of what is going on. My guess about concerns like the ones in this thread is that large, complex applications have a large number of places where code and logic errors can hide. It is not so much an issue of having a large application for the developers to test with as much as it is having one with particular errors and/or interactions between different programming aids packages. Perhaps if somewhere in the browser and/or related elements like FB it could be possible to have some sort of an option to give more extensive information about what is going on inside. I suspect some of the most common issues around typos and the like have somewhat typical characteristics from the browser's point of view. Maybe more of that sort of thing could have options for being reported during development. Example- buried in the typical browser there are points where syntax errors are compensated for. Most all the browsers tolerate a lot of erroneous code and do their best to move on rather then rejecting a page. Maybe it would be possible to have an option to expose those events. It would give developers a better chance to discover the source of problems (and maybe also help build high quality code in general). -- 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.
