If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 15/Oct/13 06:18 PM
Updated: 15/Oct/13 06:18 PM
|
|
|
Component/s: |
None
|
Affects Version/s: |
5.0.36
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
Environment:
|
Browser issue
|
|
We throw exceptions upon build submission as a method to validate user input. We would like the user to press the browser back button to adjust their build option selections and then resubmit.
I have observed that when you launch a build in QuickBuild using the play button, the selections you make prior to an initial exception being thrown are the selections QuickBuild will always remember during that run.
For example, if you press the back button after the initial exception, reselect other options from the available controls, then throw a second exception, and then once again press the browser back button - the selections you made immediately prior to the second exception are not displayed. Instead, the controls reflect the state they were in prior to the first thrown exception. After that, it does not matter how many exceptions you throw, the controls will always be reset to the state they were in prior to the initial thrown exception.
In my testing I found that it is consistent across all QuickBuild controls and happens regardless of the browser used.
When exceptions are thrown upon build submissions and the browser back button is pressed, the form controls should reflect the state they were in immediately prior to the thrown exception.
|
Description
|
We throw exceptions upon build submission as a method to validate user input. We would like the user to press the browser back button to adjust their build option selections and then resubmit.
I have observed that when you launch a build in QuickBuild using the play button, the selections you make prior to an initial exception being thrown are the selections QuickBuild will always remember during that run.
For example, if you press the back button after the initial exception, reselect other options from the available controls, then throw a second exception, and then once again press the browser back button - the selections you made immediately prior to the second exception are not displayed. Instead, the controls reflect the state they were in prior to the first thrown exception. After that, it does not matter how many exceptions you throw, the controls will always be reset to the state they were in prior to the initial thrown exception.
In my testing I found that it is consistent across all QuickBuild controls and happens regardless of the browser used.
When exceptions are thrown upon build submissions and the browser back button is pressed, the form controls should reflect the state they were in immediately prior to the thrown exception. |
Show » |
No changes have yet been made on this issue.
|
|