Thank you for the info Thiago! Unfortunately this seem to indicate that
a sledgehammer needs to be taken to the task :( I've experimented with
disabling Blackbird (which is fairly trivial using the correct symbol)
but this doesn't disable T5's JS error capturing. I'll try if putting it
in production mode will do the trick instead...
Could possibly be that it's prototype which is capturing my errors since
I have code running on page-load using a custom tapestry initializer...
Cheers
On 03-05-11 17:51, Thiago H. de Paula Figueiredo wrote:
On Tue, 03 May 2011 12:13:15 -0300, Martin Reurings
<mar...@windgazer.nl> wrote:
Hi guys,
Hi!
Perhaps my google-fu is too weak, perhaps it's something nobody else
has had an issue with, but T5's built in javascript error-handling
keeps getting in the way of development :( Sometimes it's quite
useful in providing me T5 related hints concerning my errors but more
often than not I'd rather just get the error in my firebug console...
See
http://tapestry.markmail.org/search/?q=clientinfrastructure#query:clientinfrastructure+page:1+mid:vuehv5hu2hsi7lyp+state:results.
By the way, Blackbird (the JavaScript console) can be easily disabled
since 5.2, I think.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
