|
If you were logged in you would be able to see more operations.
|
|
|
Trails
Created: 02/May/07 05:01 PM
Updated: 30/Aug/07 08:56 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
1.0.0
|
| Fix Version/s: |
1.1.0
|
|
|
Issue Links:
|
Related
|
|
This issue relates to:
|
|
TRAILS-35
To avoid double submit and refresh issues we should implement some sort of "redirect after post" pattern
|
|
|
|
|
|
|
|
|
This can cause some issues with validation, for instance the "cancel" button is causing a tapestry validation in the server.
To test it you can edit an object from a child collection, fill the form with invalid values and then hit cancel. the error messages will appear in the parent page.
|
|
Description
|
This can cause some issues with validation, for instance the "cancel" button is causing a tapestry validation in the server.
To test it you can edit an object from a child collection, fill the form with invalid values and then hit cancel. the error messages will appear in the parent page. |
Show » |
|
Bug
Now we are using the submitType "cancel" value to avoid validation in the server when the user hits the cancel button.
But we can't use "success" because we have more than one success target (Apply & Save)