| Issue 288: | Adding child with "addChild()" causes parent to become selected | |
| 2 people starred this issue and may be notified of changes. | Back to list |
What steps will reproduce the problem? ------------------------------------------ Demo: http://jsfiddle.net/t77yQ/2/ 1. Create a new tree with "checkbox: true" and any of the selection modes. 2. Get a handle to the root node, and call addChild() to create a new 1st level node. This node is NOT selected, which makes sense. 3. Get a handle to the new 1st level node and call addChild() to create a new 2nd level child. Note that the 1st level node [created in step 2] now shows up as selected! What is the expected output? What do you see instead? -------------------------------------------------------- The expected result is that adding a child node should not cause an unselected parent to become selected. Software versions --------------------------------------------------------- Dynatree 1.2.1 RC3 jQuery 1.4.2 and 1.7.1 [observed in both] Occurs in Chrome, Firefox 9 and IE 9 on Windows. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
Feb 28, 2012
Project Member
#1
moo...@wwwendt.de
Labels:
Milestone-Release1.2.1
Jun 6, 2012
Deferred, so v1.2.1 can be released shortly.
Labels:
-Milestone-Release1.2.1 Milestone-Release1.2.2
Oct 6, 2012
(No comment was entered for this change.)
Labels:
-Milestone-Release1.2.2 Milestone-Release1.2.x
May 1, 2014
As of 2014 Dynatree is feature frozen. Please have a look at Fancytree (sequel of DynaTree 1.x): chances are good that the problem was resolved / the requested featuer is already implemented. Please open a new issue there otherwise: https://github.com/mar10/fancytree
Status:
WontFix
May 3, 2014
(No comment was entered for this change.)
Labels:
-Milestone-Release1.2.x Milestone-Release2.0
|