That does seem odd. IE gets the least coverage, at least by me, since I can
only run it in a VM, and it has the worst debugging experience of any
browser. This still seems quite fishy though ... since when can you not
call() a Function?
On Mon, Jun 25, 2012 at 3:03 PM, Ray Nicholus <rnicho...@widen.com> wrote:
> I'm seeing the following javascript exception in IE only when the
> ajaxRequest function is called in tapestry.js:
>
> Object doesn't support property or method 'call'
>
>
> I've confirmed that successHandler is not null, and call appears to be
> available as a native function. as one would expect. Any idea what is
> going on here? The code below is from ajaxRequest in tapestry.js.
>
>
> try {
> /* Re-invoke the success handler, capturing any
> exceptions. */
> successHandler.call(this, response, jsonResponse);
> } catch (e) {
> finalOptions.get('onException').call(this,
> response);
> }
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
