The FormFragment component should isolate its action stream (t:formdata hidden
field) such that the entire client-side element may be removed
---------------------------------------------------------------------------------------------------------------------------------------------
Key: TAPESTRY-2393
URL: https://issues.apache.org/jira/browse/TAPESTRY-2393
Project: Tapestry
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.0.11
Reporter: Howard M. Lewis Ship
FormFragment currently "collects" actions but ultimately embeds them in the
form itself. It also uses a hidden form field to control whether the actions
for the fragment are executed on the server side.
An alternative approach would be for the fragment's actions to be stored in its
own hidden field. On a form submit, the fragment could remove the element and,
thus, no update to the server for those fields and no need to maintain the
"enabled/disabled" form field.
This also has additional applications for use with FormInjector and Ajax forms
wherein rows can be easily added and removed from the client-side.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
