Hi,
In debug mode, if a ScheduledCommand throws an AssertionError then 
SchedulerImpl will never ever flushFinallyCommands() cause of entryDepth 
value greater than 0.

I I look at flushFinallyCommands and then runScheduledTasks I discovered 
that it catch RuntimeException (Hidden exception) but not Error.

This behavior make the page very unstable in debug mode for my bug. The 
expected behavior is to display my initial AssertionError in the console.

Do i Have to fill a bug ?


thanks

laurent

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Reply via email to