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
Hello! I've been having difficulty getting d3.csv() in D3v5 to work nicely on localhost in Chrome.
I've made a barebones example here that reproduces the error on both my Mac and Windows machines (latest OS version), in Chrome (latest release version).
When I first load the page, it takes some time before the data arrives. When I check the network tab on my dev tools, it shows up as "pending". It finally arrives after about 30-90 seconds.
When I run the same code through Github pages the error doesn't occur and the console.log happens fine. When I run the same code on localhost in Safari on my Mac, or Firefox on my Windows machine, the error doesn't occur and the console.log happens fine.
Don't hesitate to ask if I can do any further testing to help isolate the issue.
The text was updated successfully, but these errors were encountered:
There’s really nothing in this library other than direct calls to the standard Fetch API, so I’m afraid I’m going to redirect you to Stack Overflow if you’d like help using Fetch and/or running a local web server.
For what it’s worth, using http-server, it took about 50ms to download line.csv on my machine.
Hello! I've been having difficulty getting d3.csv() in D3v5 to work nicely on localhost in Chrome.
I've made a barebones example here that reproduces the error on both my Mac and Windows machines (latest OS version), in Chrome (latest release version).
When I first load the page, it takes some time before the data arrives. When I check the network tab on my dev tools, it shows up as "pending". It finally arrives after about 30-90 seconds.
When I run the same code through Github pages the error doesn't occur and the console.log happens fine. When I run the same code on localhost in Safari on my Mac, or Firefox on my Windows machine, the error doesn't occur and the console.log happens fine.
Don't hesitate to ask if I can do any further testing to help isolate the issue.
The text was updated successfully, but these errors were encountered: