Hi,
I would like to understand the 'Back' button.
My 'form A' includes no-cache headers. From 'form A' I submit to 'form B' or to a script that redirects back to 'form A'. Within 'form B' (or the other script that redirects back) I make changes to session variables that hold the values displayed in 'form A'. When I click 'Back' to 'form A' should I expect to see the prevous values in the form elements of 'form A' as they were displayed previously or should i expect (because of the no-cache' headers) to see the updated 'form A' as reflected from the current session variables?
Currently I see the previous 'form A'.
I would prefer that the form always display the current values when the user goes 'Back'.
If someone would shed some light on this I would very much appreciate it.
I have a feeling that my note below may not be understood well, if not, all I really need is an answer to the above general case.
Thanks
Note:
In my special case, 'form A' includes a list of rows to which the user can add and delete. If the user submits the 'Add Row' button, a row is added and remain on 'form A'. Then clicks 'Back', what happens is that, on one hand, the list stays the same size (even though in the previous 'form A' screen the list had less rows), but on the other hand, the values inside the form elements change to their previous values.
Since the user can also add/remove rows, after several 'Back' clicks, the list displays completely wrong values in the form (values that were never input by the user).
