On Wed, Sep 9, 2009 at 05:07, Matthew Gregory
<[email protected]<matthew%[email protected]>
> wrote:
> We are using Firebug 1.4.2 and Firefox 3.5.2 on Windows and it is a
> problem for us as well. We get the timeout if an error is thrown unless
> we wrap it in a try/catch
>
> No, this is not the issue Christian is requesting help with. The timeout
issue has been fixed in trunk, so you should upgrade. The problem Christain
references is the fact that even with the timeout problem fixed, he is not
seeing a javascript error be displayed if a syntax error (or in his test
case, a call to an undefined function) occurs *in* the "completed" handler,
whereas he does see a javascript error if an error occurs outside of the
"completed" handler. I, in my testing, do not have this problem. I get the
error displayed in Firebug whether or not it's in the handler function.
Derrell
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
