You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using qdt-component in a two built using Vue2 and react and have found that some users are consistently encountering an issue where the charts never actually load and instead continually show the loading animation.
This appears to occur because Require.js is not loaded when the component attempts to render as when the issue occurs we see the following message logged to the console:
The peculiar thing about this particular issue is that only some users experience it when visiting these sites and others may not experience it at all or only intermittently. In most cases it appears that refreshing the browser can/will resolve the issue but, it can/will occur again.
Given the inconsistent nature of the issue, it would seem to be related to some asynchronous operation occurring within the component. Is this something that there is a known work around or resolution for?
The text was updated successfully, but these errors were encountered:
Sorry for the delay, I've been away on vacation lately. Is there any updated documentation for using Vue with the latest 3.0 version? I noticed the React and Angular documentation was updated while the Vue documentation was not.
It seems like we may need to complete some significant revisions of our code before we can test the latest, so any information on this is greatly appreciated (particularly in regards to the changes around using picasso settings, if you have any examples that would be really helpful for my understanding).
Thanks again for your attention on this issue, I will continue to update as the situation develops.
We are using qdt-component in a two built using Vue2 and react and have found that some users are consistently encountering an issue where the charts never actually load and instead continually show the loading animation.
This appears to occur because Require.js is not loaded when the component attempts to render as when the issue occurs we see the following message logged to the console:
The peculiar thing about this particular issue is that only some users experience it when visiting these sites and others may not experience it at all or only intermittently. In most cases it appears that refreshing the browser can/will resolve the issue but, it can/will occur again.
Given the inconsistent nature of the issue, it would seem to be related to some asynchronous operation occurring within the component. Is this something that there is a known work around or resolution for?
The text was updated successfully, but these errors were encountered: