Yusuf Canbaz

I also observed this. Probably the reason is when a compound node is collapsed, its children are removed from cy. When we expand a meta edge, source or target of...

> any updates? It is about user behavior. You should not let the user expand such an edge.

Hi @Alexithemia Collapsed edges are stored inside the data property `collapsedEdges`. So you can read them like `edge.data('collapsedEdges')`. Note that, edges inside this data property can also contain **collapsedEdges**. So...

No, it is not simple. Why don't you follow what I said? Just a recursive function and iterate through all edges and their collapsed children. Also here what is a...

@Alexithemia iterating through 4000+ edges should be fast if your algorithm is linear (it should be). Did you try that? Secondly, collapsing edges is done manually by the API user....

You should write a recursive function and find the collapsed node. Collapsed nodes are removed from cytoscape.js but they stay in the memory. You should investigate `collapsedChildren` properties

@Alexithemia I think if you are going to add **NEW** elements to collapsed children, you should add them to Cytoscape.js. Otherwise, there is no similar thing to a node "constructor"...

Ok. Still you can use `getCollapsedChildrenRecursively` and/or `getAllCollapsedChildrenRecursively` methods to achieve this easily.

In case you are interested, I created a kind of extended version of your data https://github.com/canbax/derman Basically it also contains some data properties.

I observed similar things with an angular app before. It goes away after you click or pan, zoom to the canvas. It might hide the context menu items later with...