[ http://issues.apache.org/jira/browse/TAPESTRY-540?page=comments#action_12318394 ]
Mind Bridge commented on TAPESTRY-540: -------------------------------------- I was actually thinking of deprecating FormTable, and making Table form-aware, similar to the For component. In other words, that will combine Table and FormTable. The component will also have a 'volatile' parameter to turn off the hidden fields if that behaviour is not desired. Is that solution okay? > All For and If components in the non-form table family should be declared as > volatile > ------------------------------------------------------------------------------------- > > Key: TAPESTRY-540 > URL: http://issues.apache.org/jira/browse/TAPESTRY-540 > Project: Tapestry > Type: Improvement > Components: Contrib > Versions: 4.0 > Reporter: Marcus Brito > > ... to avoid the creation of lots and lots of hidden form values, when the > user doesn't need them. If the user actually needs the table state to be kept > on the form, he should use TableForm and friends. -- 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]
