We have a bunch of requirements about “saving state across navigation”
Legacy tools should not save state
http://bugs.sakaiproject.org/jira/browse/REQ-285
Sakai remembers state – optional?
http://bugs.sakaiproject.org/jira/browse/SAK-737
Sakai Saving State – Moving between tools and within pages of a tool should behave conistently for users.
http://bugs.sakaiproject.org/jira/browse/REQ-37
Basically the use case is simple – every time you move between tools or between sites, the tool that you “come back to” needs to be at its initial screen.
In Sakai 2.2 – when you “come back” you are brought back to where you left and the tool is in the state you left it.
As an example:
Go to resources – press the Add button – Go to Home – Go Back to Resources – what do you see?
In the state saving approach – you are at the Add screen – in the state clearing approach you are at the top of the resources hierarchy as if you pressed Resources for the first time.