You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Mark Reynolds (JIRA)" <ta...@jakarta.apache.org> on 2006/08/20 17:57:15 UTC
[jira] Created: (TAPESTRY-1072) Form still validates field removed
with AJAX on first submit.
Form still validates field removed with AJAX on first submit.
-------------------------------------------------------------
Key: TAPESTRY-1072
URL: http://issues.apache.org/jira/browse/TAPESTRY-1072
Project: Tapestry
Issue Type: Bug
Components: Core
Affects Versions: 4.1.1
Environment: tapestry 4.1.1-20060819.225847-18
Reporter: Mark Reynolds
Attachments: mintap.zip
When a form field is dynamically added to a form using @EventListener//ResponseBuilder and the form is submitted, the validation on the new field works correctly. But when the field is removed using the same technique, the removed field still gets validated on the next submit.
The attached project reproduces this issue.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Resolved: (TAPESTRY-1072) Form still validates field removed
with AJAX on first submit.
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-1072?page=all ]
Jesse Kuhnert resolved TAPESTRY-1072.
-------------------------------------
Fix Version/s: 4.1.1
Resolution: Fixed
Fixed. I wish everyones jira issues came with completely self contained/documented examples :)
> Form still validates field removed with AJAX on first submit.
> -------------------------------------------------------------
>
> Key: TAPESTRY-1072
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1072
> Project: Tapestry
> Issue Type: Bug
> Components: Core
> Affects Versions: 4.1.1
> Environment: tapestry 4.1.1-20060819.225847-18
> Reporter: Mark Reynolds
> Assigned To: Jesse Kuhnert
> Fix For: 4.1.1
>
> Attachments: mintap.zip
>
>
> When a form field is dynamically added to a form using @EventListener//ResponseBuilder and the form is submitted, the validation on the new field works correctly. But when the field is removed using the same technique, the removed field still gets validated on the next submit.
> The attached project reproduces this issue.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Assigned: (TAPESTRY-1072) Form still validates field removed
with AJAX on first submit.
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-1072?page=all ]
Jesse Kuhnert reassigned TAPESTRY-1072:
---------------------------------------
Assignee: Jesse Kuhnert
> Form still validates field removed with AJAX on first submit.
> -------------------------------------------------------------
>
> Key: TAPESTRY-1072
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1072
> Project: Tapestry
> Issue Type: Bug
> Components: Core
> Affects Versions: 4.1.1
> Environment: tapestry 4.1.1-20060819.225847-18
> Reporter: Mark Reynolds
> Assigned To: Jesse Kuhnert
> Attachments: mintap.zip
>
>
> When a form field is dynamically added to a form using @EventListener//ResponseBuilder and the form is submitted, the validation on the new field works correctly. But when the field is removed using the same technique, the removed field still gets validated on the next submit.
> The attached project reproduces this issue.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org