thanks for reporting. This is a current limitation of the visualization framework we are using. We are already in contact with the creators and I hope we can offer a better solution soon. We are also looking into solutions while this problem still exists in the visualization framework. I will post something in this thread as soon as I have a solution.