Skip to content

Unknown filename when exporting charts (Safari) #1227

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

Closed
wallacedf opened this issue Dec 6, 2016 · 14 comments · Fixed by #5838
Closed

Unknown filename when exporting charts (Safari) #1227

wallacedf opened this issue Dec 6, 2016 · 14 comments · Fixed by #5838
Labels
bug something broken
Milestone

Comments

@wallacedf
Copy link

Hi,

I've been using the "Export" feature to save charts as images and it's working mostly great! However, in Safari 10.0.1 (Mac OSX), the file is downloaded with the name "Unknown" without even an extension.

Here is an example: https://plot.ly/~bd_plotly/46

Could you please check this issue out?

Thank you very much!

@etpinard etpinard added bug something broken community community contribution labels Dec 6, 2016
@freshwuzhere
Copy link

freshwuzhere commented Dec 16, 2016

ditto. Is this in Safari only? Firefox has correct behaviour and can store many images. No folder control though.

@meletis
Copy link

meletis commented Dec 16, 2016

Yes, this is Safari OS X only.

@alubbock
Copy link

In plotly 1.27.1 and Safari 10.1.1, the user gets two image downloads - one with the proper filename and one with filename "Unknown". The Javascript console also shows the error:

data:application/octet-stream;base64,<octet stream goes here>=
Failed to load resource: Frame load interrupted

@petermattia
Copy link

I have the same issue in Safari as @alubbock. Works fine on Chrome.

@abegehr
Copy link

abegehr commented Jun 27, 2018

same problem here. downloading the image twice (Unknown.png and [name].png) on OSX 10.13.5 Safari 11.1.1 with Plotly 1.38.1

@ibrewster
Copy link

This appears to still/again be an issue two years later, with plotly.js v1.54.2. Is there any workaround (other than telling the user Sorry! Your browser of choice doesn't work for me! :-p)?

@DanielMedic
Copy link

And it's still happening two years after @ibrewster 's comment. :/

@archmoj archmoj removed the community community contribution label Oct 30, 2020
@rlreamy
Copy link
Contributor

rlreamy commented Apr 23, 2021

Just going to chime in with the same question as several others have asked...is this something that is going to be fixed soon, or is there a workaround for this?

@nicolaskruchten
Copy link
Contributor

This issue is not on anyone's roadmap at the moment, although we certainly would be happy to review and accept a pull request that resolves it :)

@rlreamy
Copy link
Contributor

rlreamy commented Apr 26, 2021

I have made some local changes to the filesaver.js and tested on Safari Version 14.0.1 (16610.2.11.51.8) and was able to get a plot to download successfully. The change I made was to simply remove the special Safari handling code in that function...it appears that at least the version of Safari I am using does not need this.

I do not have other versions of Safari to try this out on, and am unsure of which versions you need supported. I also tried to create a pull request with my changes but was denied access.

Let me know how I can proceed with pushing this code to the repo so that others can test it and it can possibly be integrated into the next release.

@archmoj
Copy link
Contributor

archmoj commented Apr 26, 2021

I have made some local changes to the filesaver.js and tested on Safari Version 14.0.1 (16610.2.11.51.8) and was able to get a plot to download successfully. The change I made was to simply remove the special Safari handling code in that function...it appears that at least the version of Safari I am using does not need this.

I do not have other versions of Safari to try this out on, and am unsure of which versions you need supported. I also tried to create a pull request with my changes but was denied access.

Let me know how I can proceed with pushing this code to the repo so that others can test it and it can possibly be integrated into the next release.

Sounds good.
@rlreamy
Please note that in order to open a PR you need to "fork" plotly.js and push the changes to that fork.

@rlreamy
Copy link
Contributor

rlreamy commented Apr 26, 2021

Thanks! Will do!

This was referenced Apr 26, 2021
@rlreamy
Copy link
Contributor

rlreamy commented Apr 26, 2021

Sorry if I did that wrong...feel free to close the one that is wrong.

@jneilliii
Copy link

So this appears to be the only issue related to the problem a user is experiencing with my project. Related issue can be seen here. I'm using Plotly.downloadImage in my code here and the image is created but with an empty surface mesh, only legend. I'm using version 2.1.0 gl3d bundle. Any help would be greatly appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something broken
Projects
None yet
Development

Successfully merging a pull request may close this issue.