When you load Tapestry components in an ajax request a new t:id is generated. Presumably because it's possible for a component with the same original id to still be on the page. I'm not sure how this relates to the client side id. -- View this message in context: http://tapestry-users.832.n2.nabble.com/How-to-fix-the-id-attribute-of-a-select-component-tp5999701p6001123.html Sent from the Tapestry Users mailing list archive at Nabble.com.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
