As you are probably aware, there is only one instance of the zone component. This one instance is rendered multiple times to produce many clientside elements.
t:id is the serverside id, id is the clientside id(s). They don't need to match. On 3 Sep 2014 20:32, "John" <j...@quivinco.com> wrote: > doesn't the t:id need to be unqiue as well, or does the framework handle > this? > ----- Original Message ----- > From: Lance Java > To: Tapestry users > Sent: Wednesday, September 03, 2014 8:05 PM > Subject: Re: dynamic ids for zones > > > Yes, and id="prop:myClientId" can produce a different, but predictable, > id > each time through the loop. > On 3 Sep 2014 19:36, "John" <j...@quivinco.com> wrote: > > > Hi, > > > > Because the zone is reused elsewhere in the page I don't want to > > explicitly name the Id because that does not generate a unique Id for > > rerendering. I need a fresh Id for each successive render, and O need > to > > know that Id in my javascript and the page. > > > > John > > ----- Original Message ----- > > From: Lance Java > > To: Tapestry users > > Sent: Wednesday, September 03, 2014 5:46 PM > > Subject: Re: dynamic ids for zones > > > > > > zone="^" is a clientside concept and means find the first parent > zone to > > the element which fired the event. > > > > I'm assuming you know you can explicitly define the zone id using: > > <t:zone t:id="serverId" id="prop:myClientId" /> > > > > > > --- > > This email is free from viruses and malware because avast! Antivirus > > protection is active. > > http://www.avast.com > > > > > --- > This email is free from viruses and malware because avast! Antivirus > protection is active. > http://www.avast.com >
