Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Redesign CSV export to improve usability
See original GitHub issueOriginal title: Set content type for CSV so that browsers will attempt to download instead opening in the browser
Right now, if the user clicks on the CSV related to a table or a query, the response header for the content type is
“content-type: text/plain; charset=utf-8”
Most browsers will try to open a file with this content-type in the browser.
This is not what most people want to do, and lots of folks don’t know that if they want to download the CSV and open it in the a spreadsheet program they next need to save the page through their browser.
It would be great if the response header could be something like
'Content-type: text/csv');
'Content-disposition: attachment;filename=MyVerySpecial.csv');
which would lead browsers to open a download dialog.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Good call! I’m doing a refactor #1518 right now which will hopefully bring the functionality of those two much closer - I’ll make a note to consider this there too.
another way to get the behavior of downloading the file is to use the download attribute of the anchor tag
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#attr-download