Alexis Jacomy

Thanks for your feedback. Yes, I think we should close this issue, as the new story addresses well enough for now.

@oda79 Thanks for that report! I totally get this issue, and that's bad, and I have no idea how to solve it yet. Maybe something with z indexing, I'll try...

Just to keep you updated, I started digging, and enabling the depth buffer might be the solution, though it kinda collides with alpha blending at the moment. I'll keep trying...

Update:  I found a way to fix the issue using the `discard;` GLSL instruction ([source](https://vis.social/@jacomyal/112710352013943593)). Unfortunately, it supposedly has a bad impact on performances... So I keep looking, but...

FYI I've been working on a fix these last days, and it starts working: https://github.com/jacomyal/sigma.js/tree/fix-1427 The main issue that remains is that using `discard;` means that we cannot draw behind...

After some more digging, it appears that one solution to solve that glitch would be to implement some "order independent transparency" technique, such as [this one](https://tsherif.github.io/webgl2examples/oit.html).

Hello, There is none yet. However, I've plugged sigma.js in a Vue application once, and the process is quite the same as with React and Angular: 1. Create a component,...

Thanks for the update!

I get the point here, but it's not very easy to know what parameters should be included and which ones shouldn't.

This issue is very legit, I just couldn't find the time to tackle it properly yet.