The problem with the DFlex approach is it calculates coordinates and positions internally without calling browser API. While this approach considers very lightweight and allows to scale the number of interacted elements without causing any problem it has a trade-off. If one number is calculated wrong it affects all other node dependencies. One solution to this problem is considering a save mode to minimize error boundaries. Anyway, I'll investigate it and see where things go wrong. Thanks for your feedback, I appreciate it.