Hover brings up a double viewer (Firefox on a Mac). It is worse with the videos than images, because the 2nd viewer never finishes loading. It spins and spins. Clicking on the 'x' to delete the viewer doesn't work. There are two reliable ways to get out of the load: (1) move off of both views (without moving either of them to pin them), or (2) click on another point, which terminates the blank window and brings up a new video, then move off of the new viewer to release it.
In terms of reproducibility, it happens the first time you hover over a point (i.e. the video must be loaded from the cluster and isn't in the cache). Once the video has been loaded, hovering over that point again will only bring up one copy. So the issue is with a cache miss. My guess is that during a cache miss, the call is repeated, which brings up the second viewer. The first viewer can never finish since it is still trying to load from cache. The second viewer completes since it is pulling a fresh copy...just my guess.
I just switched to an image media for hover and tried that approach (hovering over a new point for the first time) and saw a similar double image, though it does complete the load. However, I was able to pull the top one over to the side and see that they both had the same id number. So, whatever is going on is probably a similar bug.
Hover brings up a double viewer (Firefox on a Mac). It is worse with the videos than images, because the 2nd viewer never finishes loading. It spins and spins. Clicking on the 'x' to delete the viewer doesn't work. There are two reliable ways to get out of the load: (1) move off of both views (without moving either of them to pin them), or (2) click on another point, which terminates the blank window and brings up a new video, then move off of the new viewer to release it.
In terms of reproducibility, it happens the first time you hover over a point (i.e. the video must be loaded from the cluster and isn't in the cache). Once the video has been loaded, hovering over that point again will only bring up one copy. So the issue is with a cache miss. My guess is that during a cache miss, the call is repeated, which brings up the second viewer. The first viewer can never finish since it is still trying to load from cache. The second viewer completes since it is pulling a fresh copy...just my guess.
I just switched to an image media for hover and tried that approach (hovering over a new point for the first time) and saw a similar double image, though it does complete the load. However, I was able to pull the top one over to the side and see that they both had the same id number. So, whatever is going on is probably a similar bug.