Details
-
Bug
-
Resolution: Fixed
-
Major
-
11.10.5, 12.4
-
High
-
Medium
-
N/A
-
N/A
-
Description
This can be reproduced on the Export tree if the following preconditions are met:
- you need a node that has a child pagination node
- this node must be closed and selected
Opening this node leads to this behavior:
- the first page of child nodes is loaded from the server and is displayed for a fraction of a second; the pagination node is the last of these child nodes
- since the parent node we opened was previously selected the tree attempts to select all child nodes that were just loaded
- when the pagination child node is selected it is actually activated, meaning that the next page of child nodes are loaded from the server
- this leads to a JavaScript error because the pagination node is activated too early, before the pagination node is completely drawn
TypeError: m[obj.children[i]] is undefinedjstree.js:2486:8 redraw_node http://localhost:8080/xwiki/webjars/wiki:xwiki/jstree/3.3.8/jstree.js:2486 redraw_node http://localhost:8080/xwiki/webjars/wiki:xwiki/jstree/3.3.8/jstree.js:5450 create_node http://localhost:8080/xwiki/webjars/wiki:xwiki/jstree/3.3.8/jstree.js:3884 addMoreChildren http://localhost:8080/xwiki/webjars/wiki:xwiki/xwiki-platform-tree-webjar/12.5-SNAPSHOT/tree.js:146 each jQuery addMoreChildren http://localhost:8080/xwiki/webjars/wiki:xwiki/xwiki-platform-tree-webjar/12.5-SNAPSHOT/tree.js:142
As a result of the JavaScript error the parent node is removed from the tree.