On Fri, 27 Jan 2012 03:22:58 -0200, Paul Stanton <p...@mapshed.com.au>
wrote:
Just a side note, this has caught a few users over time (since t5.1).
Boris' expected behaviour does not seem to me to be too unrealistic an
expectation! Depending on your personality type ;) you may even consider
this a bug.
Maybe the zone re-rendering process should handle this client id
changeover gracefully?
The non-developer-provided ids change because otherwise the page could
have different elements with the same id after a zone update. Automating
the EventLinks (and ActionLinks) to point at new ids is quite hard:
Tapestry would need to keep a server-side map of which link points to each
zone, figure out which ids changed and then send a (EventLink, new target
id) change them after a zone update. This would probably need to rewrite
all JavaScript code related to zones. You can avoid this by providing
client-side ids to Zones, so I don't think this whole change is worth.
--
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
