tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoff Callender (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TAP5-1896) AjaxFormLoop corrupts list when redisplayed after Remove then server-side failure
Date Wed, 04 Apr 2012 09:10:34 GMT
AjaxFormLoop corrupts list when redisplayed after Remove then server-side failure
---------------------------------------------------------------------------------

                 Key: TAP5-1896
                 URL: https://issues.apache.org/jira/browse/TAP5-1896
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.3, 5.2
            Reporter: Geoff Callender
            Priority: Critical


To see the effect use an AjaxFormLoop with input field(s) and at least 3 rows built from existing
data. It must be in a Form.

Remove row n. 
Submit, ensuring in some way that you get a server-side validation error.

The redisplayed loop will have all the right output values, but the input values will be corrupted:
- the removed row (n) will be missing (good), 
- row n+1 will be correct (good),
- every row below that will have input values that belong to the row before it (bad).

If you try the process again but this time remove 2 adjacent rows you'll get:

- the removed rows (n-1 and n) will be missing (good), 
- row n+1 will be correct (good), 
- row n+2 will be correct (good),
- every row below that will have input values that belong 2 rows before it (bad).


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message