[ https://issues.apache.org/jira/browse/WICKET-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924004#action_12924004 ]
Martin Grigorov edited comment on WICKET-3127 at 10/22/10 4:22 PM: ------------------------------------------------------------------- The patch looks OK and works fine with the quickstart application. The collapsed node does not expand when adding new sub-node. -Brix demo admin > menus still expands ...- *Update*: My bad. I was testing against the old wicket-1.4-SNAPSHOT.jar Adding and removing nodes work OK until I try to remove the root node. The quickstart fails due to its own problem, brix removes the root but then cannot add new root... >From Wicket side everything looks ok, so I will commit the patch. was (Author: mgrigorov): The patch looks OK and works fine with the quickstart application. The collapsed node does not expand when adding new sub-node. Brix demo admin > menus still expands ... Adding and removing nodes work OK until I try to remove the root node. The quickstart fails due to its own problem, brix removes the root but then cannot add new root... >From Wicket side everything looks ok, so I will commit the patch. > Adding node to a collapsed tree node should not cause it to expand > ------------------------------------------------------------------ > > Key: WICKET-3127 > URL: https://issues.apache.org/jira/browse/WICKET-3127 > Project: Wicket > Issue Type: Bug > Components: wicket > Affects Versions: 1.4.13, 1.5-M3 > Reporter: Mike Hefner > Assignee: Martin Grigorov > Priority: Minor > Fix For: 1.4.13, 1.5-M3 > > Attachments: WICKET-3127-fix.patch, WICKET-3127-QuickStart.zip > > > The fix for WICKET-3112 made a unwanted minor modification to the Tree > behavior that was established in WICKET-2886. > Adding a child to a tree node that already has children and that is currently > collapsed now causes the parent node to expand so that all the children are > displayed. Only adding the first child to a node should cause it to expand, > in all other cases the state of the parent node should not change. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.