You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cytoscape.js version : 3.23
cytoscape-expand-collapse: "^4.1.0",
Browser/Node.js & version : Chrome , 110.0.5481.180
Current (buggy) behaviour
What does the bug do?
I am trying to use the collapsedChildren method to expand and collapse on double click event. Ideally, it should return a collection of all collapsed children but sometimes even with values present it returns null.
Another related bug is, when children are returned by collapsedChildren() , inside the target object it shows as null, whereas it should have shown children elements in both cases.
Desired behaviour
What do you expect Cytoscape.js to do instead?
It should return the collection whenever any children is present. If the target.data() object is opened, we can see that collapsedChildren has values inside of it but when called , it's returning null.
Reproduce the issue :
Initialize cytoscape
Attach any event handler( dbl click in my case)
let targetData = event.target;
console.log(targetData.data() , targetData.data().collapsedChildren)
The 2nd print results in null sometimes, during that you can open the targetData.data() and check for collapsedChildren.
Download and Initialize cytoscape-expand-Collapse (optional)
Entire event handler:
var api = cy.expandCollapse('get') //expand collapse get object to run it's methods.
The bug is captured in the below screenshot. collapsedChildren under the target object which is showing as null is when I have called the latter part of this code- console.log(targetData.data() , targetData.data().collapsedChildren)
Bug screenshot where collapseChildren() returns elements but shows as null inside target
From what the method's name indicates, it should provide the collapsedChildren when tried to access but the output is behaving exactly in the reverse expected fashion.
Any comments and updates if I have misunderstood this method, is much appreciated.
Thanks for taking your time to read so far.
The text was updated successfully, but these errors were encountered:
Environment info
Cytoscape.js version : 3.23
cytoscape-expand-collapse: "^4.1.0",
Browser/Node.js & version : Chrome , 110.0.5481.180
Current (buggy) behaviour
What does the bug do?
I am trying to use the collapsedChildren method to expand and collapse on double click event. Ideally, it should return a collection of all collapsed children but sometimes even with values present it returns null.
Another related bug is, when children are returned by collapsedChildren() , inside the target object it shows as null, whereas it should have shown children elements in both cases.
Desired behaviour
What do you expect Cytoscape.js to do instead?
It should return the collection whenever any children is present. If the target.data() object is opened, we can see that collapsedChildren has values inside of it but when called , it's returning null.
Reproduce the issue :
Initialize cytoscape
Attach any event handler( dbl click in my case)
let targetData = event.target;
console.log(targetData.data() , targetData.data().collapsedChildren)
The 2nd print results in null sometimes, during that you can open the targetData.data() and check for collapsedChildren.
Download and Initialize cytoscape-expand-Collapse (optional)
Entire event handler:
var api = cy.expandCollapse('get') //expand collapse get object to run it's methods.
The bug is captured in the below screenshot. collapsedChildren under the target object which is showing as null is when I have called the latter part of this code- console.log(targetData.data() , targetData.data().collapsedChildren)
Bug screenshot where collapseChildren() returns elements but shows as null inside target
From what the method's name indicates, it should provide the collapsedChildren when tried to access but the output is behaving exactly in the reverse expected fashion.
Any comments and updates if I have misunderstood this method, is much appreciated.
Thanks for taking your time to read so far.
The text was updated successfully, but these errors were encountered: