There's some complexity in the Cytoscape component that was initially there to handle smooth transitions when adding elements to a graph, back when we were incrementally updating them, and for udpating the data
when the date range changes.

Remove this and instead remove all elements and add new elements when the elements change.

Fixes elastic#66184.

There's some complexity in the Cytoscape component that was initially there to handle smooth transitions when adding elements to a graph, back when we were incrementally updating them, and for udpating the data
when the date range changes.

Remove this and instead remove all elements and add new elements when the elements change.

Fixes elastic#66184.

There's some complexity in the Cytoscape component that was initially there to handle smooth transitions when adding elements to a graph, back when we were incrementally updating them, and for udpating the data
when the date range changes.

Remove this and instead remove all elements and add new elements when the elements change.

Fixes #66184.

There's some complexity in the Cytoscape component that was initially there to handle smooth transitions when adding elements to a graph, back when we were incrementally updating them, and for udpating the data
when the date range changes.

Remove this and instead remove all elements and add new elements when the elements change.

Fixes #66184.

After simplyfying the layout mechanism in elastic#66438, we made it so the `data` event handler would run even if there are no elements. This causes the `layoutstop` handler to run as well, but if we have multiple renders with no elements, multiple `layoutstop` events would by triggered after the elements were loaded, causing the map to jump around, which is especially visible with a single node.

Fixes elastic#66528.

After simplyfying the layout mechanism in #66438, we made it so the `data` event handler would run even if there are no elements. This causes the `layoutstop` handler to run as well, but if we have multiple renders with no elements, multiple `layoutstop` events would by triggered after the elements were loaded, causing the map to jump around, which is especially visible with a single node.

Fixes #66528.

After simplyfying the layout mechanism in elastic#66438, we made it so the `data` event handler would run even if there are no elements. This causes the `layoutstop` handler to run as well, but if we have multiple renders with no elements, multiple `layoutstop` events would by triggered after the elements were loaded, causing the map to jump around, which is especially visible with a single node.

Fixes elastic#66528.

After simplyfying the layout mechanism in elastic#66438, we made it so the `data` event handler would run even if there are no elements. This causes the `layoutstop` handler to run as well, but if we have multiple renders with no elements, multiple `layoutstop` events would by triggered after the elements were loaded, causing the map to jump around, which is especially visible with a single node.

Fixes elastic#66528.

After simplyfying the layout mechanism in #66438, we made it so the `data` event handler would run even if there are no elements. This causes the `layoutstop` handler to run as well, but if we have multiple renders with no elements, multiple `layoutstop` events would by triggered after the elements were loaded, causing the map to jump around, which is especially visible with a single node.

Fixes #66528.

After simplyfying the layout mechanism in #66438, we made it so the `data` event handler would run even if there are no elements. This causes the `layoutstop` handler to run as well, but if we have multiple renders with no elements, multiple `layoutstop` events would by triggered after the elements were loaded, causing the map to jump around, which is especially visible with a single node.

Fixes #66528.