Regenerate your listeners when you do the partial page render; get the
clientId from each field and make sure you observe changes to that
element. Don't try to predict what ids Tapestry will use.
On Thu, Jun 17, 2010 at 2:29 PM, Paul Stanton <p...@mapshed.com.au> wrote:
> I have a form which is part of a zone which gets updated regularly (for
> example, when the form is submitted).
>
> the first time the pages loads, the form and its textfield's ids are as
> expected ie exactly what is entered as t:id
> eg
> <input t:type="textfield" t:id="myTextField" />
> =
> <input type="text" id="myTextField" />
>
> however, once the zone has been updated, the ids for the form and the
> textfields within it have a code appended to them:
> eg
> <input type="text" id="myTextField-12947ccd236" />
>
>
> Unfortunately I have scripts which need to reference these fields by their
> Id, so when the Id changes the scripts break:
> eg
> $("myTextField").value = "myValue";
>
> how have other people handled this?
>
> thanks, paul.
>
> ---------------------------------------------------------------------
> 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
