nana (Jul 14 2025 at 16:56): nana (Jul 14 2025 at 16:56):I discovered an issue with Chrome and how it handles large datasets loaded by external tools. In our Dataverse instance, we have a few survey datasets that total to > 500MB of data.
These datasets load just fine while using the Data Explorer (Scholar's Portal's external tool used to view and edit dataset) in Firefox. However using Chrome, the dataset is unable to send the tabular data to the external tool. This was verified using hoppscotch.io, the online alternative to Postman. In Firefox, using Hoppscotch to query the datafile api url (e.g. https://borealisdata.ca/api/v1/access/datafile/892444) returns the tabular data as expected. In Chrome, even though the URL resolves successfully with a 200 code, an empty result is returned.
This (at least to me) to be obviously a Chrome issue, but I just wanted to bring it your attention.
Philip Durbin 🚀 (Jul 14 2025 at 17:13):Interesting. So you think the bug is in Chrome? Nothing to fix in Dataverse or in Data Explorer?
nana (Jul 14 2025 at 18:59):I believe so. The only fix I can think of for Data Explorer involves using a server to temporarily download the data to. For Dataverse, maybe delivering the data in chunks could be a solution but both of these are band-aid solutions for something that works perfectly fine in other browsers.
Philip Durbin 🚀 (Jul 14 2025 at 19:03):The thing is, Chrome is the most popular browser.
Philip Durbin 🚀 (Jul 14 2025 at 19:03):Are you inclined to open a bug with Chrome?
nana (Jul 14 2025 at 19:09):Yeah you're right. I'll try and research other ways to get around this.
nana (Jul 14 2025 at 19:09):And yes it might be best open an issue with Chrome, at least to see if this is something they're aware of and/or how long it might take to fix. It would give us an idea of how we should prioritize this.
Philip Durbin 🚀 (Jul 14 2025 at 19:13):I guess in practice it would be a bug against Chromium. 
Last updated: Nov 01 2025 at 14:11 UTC