No, you misunderstood my answer. You need to keep the same id which is
generated by tapestry in order to let tapestry processes underneath its
hood. If you want to use javascript to handle the DOM elements, you need
to use wildcard, regular expression to select the tapestry generated ID
On 12/30/2013 9:14 PM, Boris Horvat wrote:
Yea that was my idea, to use javascript code to modify the id in order for
the java side to be able to process the correct form, however this seems
like ugly solution :)
On Mon, Dec 30, 2013 at 3:10 AM, Thai Tran <bubu...@gmail.com> wrote:
It is better to use class for CSS stuffs and $("form[id^=form]") (select
the form with the id started with "form") for javascript stuffs. Tapestry
creates a new id not only on the client side but also keep track the new id
underneath the hood (for security purpose, I guess)
On 12/30/2013 4:02 AM, Boris Horvat wrote:
Hi everyone,
I have a zone around my form (pseudo code below)
<t:zone t:id="zone" id="zone">
<t:form t:id="form" id="form" t:zone="^">
// some fields
</t:form:>
</t:zone>
After the zone is submitted the value is saved, the zone is refreshed and
my form is broken.
I believe that I could write a javascript code that will capture this
event
and override the id back to the original, but is there any better way to
resolve this?
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
