Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression bugs in plotly since updating to 1.32.0 #1211

Closed
daattali opened this issue Mar 7, 2018 · 13 comments
Closed

Regression bugs in plotly since updating to 1.32.0 #1211

daattali opened this issue Mar 7, 2018 · 13 comments

Comments

@daattali
Copy link

daattali commented Mar 7, 2018

2/3 of these issues are already mentioned in #1178 but since that PR is merged, it would get lost there.

  1. When the initial dragmode is zoom and I manually click on lasso selection, the plot stretches horizontally a bit (see GIF below)

  2. Something in selecting/adding points is broken. Here is a GIF of what selecting some points and trying to add the same points back as a different colour looks like:
    plotlybugs
    This does not happen with the current CRAN version of plotly. I assume this doesn't always happen, otherwise it would be noticed and fixed by now. I cannot provide reproducible code in this issue, but @cpsievert has access to code that has this problem. The repo at https://github.com/daattali/sievert-oil is an example of this issue

  3. Points aren't showing in RStudio. Using the same app from the private repo https://github.com/daattali/sievert-oil using the CRAN version the plot works absolutely fine within RStudio, but with the current github version, nothing shows up in the plot within RStudio Viewer.

@cpsievert
Copy link
Collaborator

For (3), can you please report the console errors you are seeing?

@cpsievert cpsievert reopened this Mar 7, 2018
@daattali
Copy link
Author

daattali commented Mar 7, 2018 via email

@cpsievert
Copy link
Collaborator

Renders in RStudio on my mac. I assume you're on Windows? Does it render on in IE/Edge? Do these points render in IE/Edge? https://codepen.io/cpsievert/pen/oqvjXa

@daattali
Copy link
Author

daattali commented Mar 7, 2018 via email

@cpsievert
Copy link
Collaborator

Ok, unfortunately I haven't been able to replicate (1) or (2). Do these problems happen universally (e.g. different browsers and states)?

@nicolaskruchten
Copy link

I wonder if some of this stuff won't have been fixed by plotly/plotly.js#2437 ...

@daattali
Copy link
Author

daattali commented Mar 7, 2018 via email

@cpsievert
Copy link
Collaborator

@daattali just upgraded to plotly.js 1.35.0 -- let me know if that helps/hurts anything

@daattali
Copy link
Author

daattali commented Mar 7, 2018

@cpsievert latest version does fix the first issue with the plot dimensions getting slightly resized.

But the other issues are still appearing, LASSOing points causes points to jump around while the mouse is dragging, and new points are appearing in a place they shouldn't be when done. Using the same repo that you have (sorry for anyone else here, only Carson and I can access that code) I get this now (Chrome on Win7)

(sorry for the very low quality and confusing GIF, it takes me forever to make it even when they're this bad...)

plotlybugs

@daattali
Copy link
Author

daattali commented Mar 8, 2018

@cpsievert after another couple hours of debugging, it seems that when I don't use toWebGL() things look and work much better

@daattali
Copy link
Author

daattali commented Mar 8, 2018

@cpsievert I was trying to debug this on my very complicated app, but it seems like these issues are happening even for the most basic plots when converted to webgl.

toWebGL(plot_ly(iris, x = ~Sepal.Width, y = ~Sepal.Length))

Doesn't show any points in RStudio, and in chrome when I try to select points, they jump around. So I think it's toWebGL() that's broken

@daattali
Copy link
Author

daattali commented Mar 8, 2018

I'm closing this as I opened individual issues with short reproducible code samples.

@daattali daattali closed this as completed Mar 8, 2018
@cpsievert
Copy link
Collaborator

after another couple hours of debugging, it seems that when I don't use toWebGL() things look and work much better

yea, plotly.js devs recently completely rewrote the webgl logic, which is why we're running into headaches -- you can always use scatter (SVG) over scattergl (canvas) and things should be less buggy, but it won't be as performant

seems like these issues are happening even for the most basic plots when converted to webgl.

Huh, I can't replicate either of these issues. If you get the same behavior on this codepen, could you please post a plotly.js issue with a screen-recording (and tag me)?

https://codepen.io/cpsievert/pen/oqvjXa

@cpsievert cpsievert added this to the scattergl weirdness milestone Mar 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants