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 <pjay...@gmail.com> 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. > > 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 of the reply ( > /Object.keys(reply.zones).each(function(zoneId) / ) as they are not defined > in the case of this component. > > After the exception no other javascript is processed. > > Regars, > Pedro Ayala > Software Developer > ProQuest > > > -- > View this message in context: > http://tapestry-users.832.n2.nabble.com/Tapestry-5-3-and-progressive-display-tp6664856p6664856.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org