Yes, but in this case, I don't see any potential for conflicts. After the zone update, you will still have one select element, but with a new id. This seems to have tripped up people who are new to Tapestry.
My question is, does it not make sense to perhaps add a parameter to the zone component so that the developer can basically say, "I know what I am doing, and I don't want the ids to be updated please", something like <t:zone ... updateIds="false" ...>? I know we can work around this by using CSS classes instead of ids to reference the elements, but it's just not the natural thing to do. Benny On Tue, Feb 8, 2011 at 10: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. > > > > 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 > >
