Issue 5: Persistence using cookies
Status:  Verified
Owner:
Closed:  Nov 2008
Project Member Reported by moo...@wwwendt.de, Aug 30, 2008
Refreshing a page should retain the current selection.

For lazy trees this may require re-loading the parent folders.
For better user experience, we should be able to display the selected node
and parent nodes immediately. And the we can use Ajax to load the missing
siblings.
So the cookie must not only contain the selected key, but also title, icon
and keys of the parens.
Nov 2, 2008
Project Member #1 moo...@wwwendt.de
As a first thing, I started implementing persistence of the expansion state.
Setting 
 options.persist: true,

will do the following:

 - Maintain a list of expanded nodes
 - If no cookie exists, create one, using the expand flags from the node data.
 - If a cookie exists, read the expand list from the cookie and use it instead of
node data.

Restrictions so far:
 - nodes must have a key
 - session cookies are used (discarded when the browser is closed)
 - $.cookie plugin is required
 - selection status is not persisted
 - lazy nodes are not supported
Status: Started
Labels: -Milestone-Discussion Milestone-Release0.3
Nov 30, 2008
Project Member #2 moo...@wwwendt.de
(No comment was entered for this change.)
Status: Fixed
Jul 17, 2012
Project Member #3 moo...@wwwendt.de
considered verified
Status: Verified