[ http://issues.apache.org/jira/browse/TAPESTRY-1131?page=comments#action_12457468 ] Andreas Andreou commented on TAPESTRY-1131: -------------------------------------------
This works great for me, but it has demonstrated another issue when some Tapestry's script files try to use the clientId in order to create javascript identifiers for variables. I'll open a new issue describing this. > Hidden Component (maybe all FormComonents?) don't get ids assigned on a page > basis. > ----------------------------------------------------------------------------------- > > Key: TAPESTRY-1131 > URL: http://issues.apache.org/jira/browse/TAPESTRY-1131 > Project: Tapestry > Issue Type: Bug > Components: Core > Affects Versions: 4.1.1 > Reporter: Patrick Moore > Assigned To: Andreas Andreou > Fix For: 4.1.1 > > > 1. create a component with a form containing a hidden field > 2. instantiate this component twice on the same page > 3. look at generated source. > notice that both hidden fields have the same id. This screws up javascript > trying to use javascript functions to get the unique hidden field. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
