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. On Tue, 2011-02-08 at 12:56 -0200, Thiago H. de Paula Figueiredo wrote: > On Tue, 08 Feb 2011 12:50:57 -0200, Benny Law <benny.mk....@gmail.com> > wrote: > > > I understand that Tapestry is doing this to avoid potential conflicts, > > but can somebody provide a real example of when this is necessary? > > Anytime you could have the same id used twice in a page, something that is > forbidden by HTML and causes lots of confusion in JavaScript and CSS. This > can happen in at least two situations: loops and AJAX updates. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org