I wish that I could answer the original question, but I can't.  

In my experience all of the browsers seem to have their own internal
algorithm for what errors that they will show and how much information about
them.  When my program breaks in one browser with no error message, then I
can usually run it in another browser and get an error message.  And of
course I don't know if qooxdoo is not feeding the error message to the
browsers in the way that they understand it or not.  It is not a showstopper
for me, but it may be much more important in somebody else's development
environment.

tom



Guilherme Aiolfi wrote:
> 
> I guess it's more a firebug's bug than qooxdoo's.Chrome never missed an
> error (that I'm aware of).
> That's a shame because firebug used to be much better.
> I guess firebug is in a transition stage. They are changing some core code
> to support neat features in the future.
> But I would be interested in a workaround for the moment.
> 
> On Mon, Oct 19, 2009 at 1:54 PM, Dietrich Streifert <
> dietrich.streif...@visionet.de> wrote:
> 
>> Forgot to say that this occurs while using FireFox 3.5 with Firebug.
>>
>> Dietrich Streifert schrieb:
>> > Hello everybody,
>> >
>> > it seems that the event queues/managers/dispatchers or where the
>> > execution of the listeners happen are hiding errors in the listener
>> > functions.
>> >
>> > Is there any way to avoid this?
>> >
>> > During development I usualy want to see every error occuring to be able
>> > to debug.
>> >
>> > Any help would be great. Thank you.
>> >
>> > Best regards...
>> >
>> >
>>
>> --
>> Mit freundlichen Grüßen
>> Dietrich Streifert
>> --
>> Visionet GmbH
>> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
>> Registergericht: Handelsregister Fürth, HRB 6573
>> Geschäftsführer: Stefan Lindner
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> qooxdoo-devel mailing list
>> qooxdoo-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Prevent-event-listener-execution-from-hiding-errors-tp25959192p25963170.html
Sent from the qooxdoo-devel mailing list archive at Nabble.com.


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to