Damn. I'll have a look.
On Sun, Sep 6, 2009 at 8:04 PM, Howard Lewis Ship wrote:
> I'm concerned about this change, because tapestry.js includes some calls to
> Tapestry.Console.debug() and .error() and those will no longer work. This
> would cause runtime exceptions (including XHR problems) to
I'm concerned about this change, because tapestry.js includes some calls to
Tapestry.Console.debug() and .error() and those will no longer work. This
would cause runtime exceptions (including XHR problems) to turn into
JavaScript errors, making it harder to diagnose what's gone wrong.
Perhaps tapes