On Feb 12, 2008 11:59 AM, Gaetan de Menten <[EMAIL PROTECTED]> wrote: > Hi list, > > I've been having the following problem for quite a while: whenever I > throw an exception in a code which is executed in a callback of a > request, nothing noticeable happens, except the request just timeouts > ... > This seems to work fine but produces longer than necessary tracebacks > and also require me to modify all my callbacks. I'd like a global fix > or workaround. This might not be a Qooxdoo bug (I suspect it's rather > a firebug bug or missing feature), but nevertheless, has anybody > found a solution or another nicer workaround to this?
I discovered another related problem recently. throw new Error() doesn't actually process the thrown error until after completion of the current javascript context. For example, if you have a loop and an error is thrown in the middle of the loop, the loop keeps running to completion. Once control returns to the browser, the thrown error will be displayed in firebug. This can be easily seen by having a this.debug() call in the loop. The debug statements show that all iterations of the loop completed even though the error was thrown during some early iteration. Derrell ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
