Ok; I just created an alpha-10 to address some of the other issues Andy has hit.
On Mon, Aug 8, 2011 at 10:53 AM, pedro wrote:
> I'll take a look at it, maybe we are not using the latest alpha release (I
> think we are in alpha 9). We haven't patched that code, and there is no
> check in the zone
I'll take a look at it, maybe we are not using the latest alpha release (I
think we are in alpha 9). We haven't patched that code, and there is no
check in the zone variable, so I'll look for the latest code and let you
know.
--
View this message in context:
http://tapestry-users.832.n2.nabble.co
Are you possibly monkey-patching the code? Here's the current version of that:
processReply : function(reply) {
Tapestry.loadScriptsInReply(reply, function() {
/*
* In a multi-zone update, the reply.content may be missing, in
* which case, leave t
Thanks, I'll take a peek at this. I think it must be some unintended
consequences of other changes.
On Mon, Aug 8, 2011 at 9:13 AM, pedro wrote:
> Hi,
>
> We are currently going through the update to Tapestry 5.3 and we have found
> an issue while using the progressive display component.
>
> The
Hi,
We are currently going through the update to Tapestry 5.3 and we have found
an issue while using the progressive display component.
There is an exception in the tapestry javascript while loading the
progressive display in the processReply function. The problem is in the loop
through the zones
