View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0026477||mantisbt||ui||public||2019-12-17 17:15||2020-02-04 11:18|
|Summary||0026477: Removing the caching of pages with validation gives returns the "empty form on back" bug #3728|
|Steps To Reproduce|
What I have done:
|Tags||No tags attached.|
i think that the main problem of caching those pages is that it caused a greater bad than good.
I'm not sure on what conditions, (previously to that point in time of those changes), the back navigation would have worked in presenting the previous form values. May be because of some combination of the headers, or some specific behaviour of browsers when presented with the incosistent headers?
FYI: currently, some browsers do effectively cache the form inputs. IIRC Chrome in my experience does this. Firefox in the other hand, don't. This is a internal behaviour of the browser, that is caching the form inputs, not the whole page.
What is the point in pre-submit processing regarding the back navigation and losing the input fields?
@cproensa The reason for using "back" is that some form validation issued an error, e.g. mandatory field not set. This is something that happens frequently and should not make you loose all your input.
Any suggestion how to proceed on that?