Thanks for the hints and clarification. I was just wondering whether I
missed something obvious. I'll try to implement it using plain JS and
let you know how that went.
Many thanks though!
Regards,
Alex
On 27.06.2011 15:43, Thiago H. de Paula Figueiredo wrote:
On Mon, 27 Jun 2011 10:38:12 -0300, Taha Hafeez
<tawus.tapes...@gmail.com> wrote:
Well I don't think it is intentional, if what I have inferred is
correct then it is a bug
An alternative will be not to use a zone, instead use your own
ajax/javascript calls.
I agree that this isn't an intentional limitation. Maybe you're just
trying to use the components in a way that wasn't intended. The Tapestry
out-of-the-box AJAX support covers many scenarios but not all (and I
guess Zones including form fields inside a Zone inside a Loop is
definetely not one of them). Some scenarios are better covered with
custom JavaScript.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
