Hi Mark - the element only occurs in one block, so this shouldn't be an issue I think.
R. On Tue, 2011-02-08 at 11:48 -0600, Mark wrote: > On Tue, Feb 8, 2011 at 9:36 AM, Richard Hill <r...@su3analytics.com> wrote: > > > > Sure. But in my case I have only the one element, it's static in .tml > > and not rendered in a loop. > > > > I think maybe what's causing it is that the element (t:select) is > > contained within the zone it updates. > > If I understand your setup, you have three blocks that contain the > same id. You use zones to show them one at a time. However, I don't > think there is a way for Tapestry to know that you won't show two or > more at a time and because of this it generates a unique id for each > one. > > Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
