[jira] [Updated] (TAP5-1769) Form submitted with an ajax request should not have the ValidationTracker persist values

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade updated TAP5-1769:
---------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> Form submitted with an ajax request should not have the ValidationTracker persist values
> ----------------------------------------------------------------------------------------
>
>                 Key: TAP5-1769
>                 URL: https://issues.apache.org/jira/browse/TAP5-1769
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2
>            Reporter: Ryan How
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> When a form is submitted using Ajax, the ValidationTracker persists values until the next request. This isn't needed when using ajax (well it doesn't seem like it is needed to me, has anyone got a use for it?) and can cause issues when reloading the page or on subsequent requests because the information is stale.



--
This message was sent by Atlassian JIRA
(v6.2#6252)