Issue 345: Cookie Persistence
Status:  Invalid
Owner: ----
Closed:  Aug 2012
Reported by Frogist...@gmail.com, Aug 9, 2012
What steps will reproduce the problem?
1.  I have 4 dynatrees on one page
2.  Each dynatree has their persist property = true
3.  Two trees share similar data.  The first tree is a result of let's say all orders.
4.  Once the user hits the search button, the second tree is loaded with a subset of orders derived from the first tree (so essentially th subset of orders exists in both the first & second tree)
5.  Since both trees share similar subset of data, and persist is set to true on all trees, both trees show the nodes selected from the first tree as selected.  Even though the second tree just finished rendering, and the user has not had time to select any nodes, it is persisting the values from the first tree.


What is the expected output? What do you see instead?
1.  Each tree should keep it's own persistence cookie.  What I see happening, is that dynatree shares one cookie, amongst as many trees as you may have.
2.  All selected values, across all trees, are stored in one cookie, dynatree-select.  This causes all trees on a page to rebind to these values, regardless if these values belong to that tree or not.
3.  As a result, some trees, persist selected values, which were not selected by the user in that tree, but selected by the user in another tree
4.  What I would like to see, if possible, is each tree on a page to create it's own dynatree-select cookie, prefixed/suffixed with the tree id.  That way, it only binds to its preselected values, not all values across all trees in a page.


What version of the dynatree and jQuery are you using?
$Version: 1.2.1$
$Revision: 606, 2012-06-12 08:10:04$

On what operating system and browser?
Windows 7, All Browsers
Aug 9, 2012
#1 Frogist...@gmail.com
OK, so I'm an idiot.  Please ignore this defect post.  I just realized you have this functionality, via the cookieId.  DUH!  So sorry, for the inconvenience.
Aug 9, 2012
Project Member #2 moo...@wwwendt.de
no problem ;-) thanks forgiving the feedback!
Status: Invalid
Jan 26, 2013
Project Member #3 moo...@wwwendt.de
(No comment was entered for this change.)
Labels: Milestone-Release0.0