-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Update( ) fails if the user is interacting with the plot #2687
Comments
Yes those issues are very similar ! Is there a way for us to detect when the issue happens until it is fixed ? I did not find a catch case on the promise that fails. The only thing I found is catching all the document.windows error and look for an undefined one 😕 |
Is this the same problem I am running into in this example? Simply clicking somewhere on the plot area while it's running generates errors like these: |
* In drawData * In supplyDefaultsUpdateCalc
* In drawData * In supplyDefaultsUpdateCalc
* In drawData * In supplyDefaultsUpdateCalc
I experience the same error when dragging the plot in my ExtJs application too quickly. The traces are locked, only the axes change. After clicking once on the plot area, it works again as intended. |
Friends, I still have this issue...in version 1.41.3. Exact same error, reproduction steps and workaround (click graph and back). |
Merged into #3305 |
Hi !
I use an heatmap to represent large datasets. After plotly_relayout events I download and process data (asynchronous, can take some time), then display them. However Plotly will return an undefined error from a promise if the update is done while dragging. I used a setTimeout in the codepen to copy the behavior of my program.
CodePen : https://codepen.io/watashiku/pen/pKJJNW?editors=1010
Error message :
Steps to reproduce : drag the plot once, then quickly start dragging again and hold it one second - the bug appears if you are dragging during the update triggered by the previous drag.
It creates two major problems :
Notes :
The text was updated successfully, but these errors were encountered: