Closed jdanish closed 2 years ago
This should be fixed with 6868516b1b1046110bc85eec2751a207da16fcbb
The problem was that edge.source and edge.target is initially stored as a simple numeric id reference. Only after D3 processes the data do the edge.source and edge.target objects become nodes. So the filter logic mistakenly thought the edge's source/targets had been filtered out, so it unhighlighted the edge. This is an annoying bit of how D3 does things that has bitten us multiple times in the past.
That's annoying! Looks fixed, though! Thanks!
Fixed with #179
This is using the export branch, but may be in earlier builds
To reproduce: