On Tue, 17 Aug 2010 10:40:36 -0300, Pierce Wetter <pie...@paceap.com>
wrote:
Yes, but id kind-of-sort-of gets set by t:id already if its not set.
Setting the client id as a workaround to force the id seems bassackwards
to me. I'm wondering if this is related to 1096.
To avoid creating elements with repeated ids, when you don't provide one
explicitly, the components generate an id with a random suffix.
I'm not an English native speaker, so what's 'bassackwards'? :)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
