slifty
commented
5 years ago There is still room for improvement in the way who talks time is handled on the script level, but the spirit of this issue has been addressed (time is stored in a session and rendered properly)
In the normal tally workflow, values for fields are saved within a session (and reset after the tally is created). This is helpful because it means data is far less likely to be lost. Who Talks does not have a similar effect, which means if a user leaves or navigates back they would have to start over.
Lets give who talks a similar treatment to the standard tally -- remember submitted values and re-load them into the who talks interface.
This is somewhat related to #12, as well as #49