@lkoutsofios wrote
sometimes is that the graph is drawn with no edges.
or maybe the edges are drawn transparent? I don't set the opacity at all.
I think there is some kind of concurrency bug that can happen when layout is slow or there is too much in the DOM, like if you sit there and wait for it, the edges will draw, but if you get bored and do something else, the edges are drawn transparent when the browser or tab is backgrounded.
D3 uses requestAnimationFrame, which only runs in the foreground. The edges are supposed to transition from opacity 0 to 1. Surely it should resolve to the completed transition but maybe it gets interrupted?
Could be one of these redraw/refresh concurrency problems. Maybe it is time to namespace all the enter transitions so that they can't be interrupted.
@lkoutsofios wrote
I think there is some kind of concurrency bug that can happen when layout is slow or there is too much in the DOM, like if you sit there and wait for it, the edges will draw, but if you get bored and do something else, the edges are drawn transparent when the browser or tab is backgrounded.
D3 uses requestAnimationFrame, which only runs in the foreground. The edges are supposed to transition from opacity 0 to 1. Surely it should resolve to the completed transition but maybe it gets interrupted?
Could be one of these redraw/refresh concurrency problems. Maybe it is time to namespace all the enter transitions so that they can't be interrupted.