JSPDF-Download not working on Safari

[hanneshal]

I have an Issue generating PDF in the latest Safari. I can't get the pdf until I open it in a popup. Is there a hint to solve this without using the "Popup" Solution?

Same here (another user)
Link:
https://stackoverflow.com/questions/21755171/jspdf-not-working-on-safari

regargs (love your work) 👍

[diegocr]

What about doc.output('dataurl'); ?

[hanneshal]

That works for inline, but there is no download like in Chrome or FireFox. The has to use "Save as" or the built in viewer. Works but the different behavior is confusing. Is there a way to "force" the download in Safari?

regards

[diegocr]

I'm neither a Safari developer nor user, so i'm not aware of the specific limitations of that browser and/or the available workarounds for them, i'm sorry.

However, you didn't mentioned what exact issue you're experiencing, I.e what happens exactly by calling doc.save('Test.pdf') - is there any error in the web console? Also, fwiw, in the last dist files i've wrapped the save/output function in a try/catch block and therefore any error throw in our code should be reported using an alert call, so feel free to give it a try.

[hanneshal]

OK, I'll have a look and report it here.

[hanneshal]

I checked the console log and there is no error or warning.

The exact issue:
You open a example page ( https://gist.github.com/hanneshal/9047565 ) in Chrome or FF you get an instand download. If you use Safari you get a simple white page, rendered without any errors or alerts and no alerts. If I use doc.output('dataurl'); Safari shows the PDF inline.

[MrRio]

This must be something to do with the Blob code. If anyone has seen any working 'saveAs' blob examples for Safari we can start there and see what we're doing differently. 

On Mon, Feb 17, 2014 at 9:38 am, Johannes Nickel <notifications@github.com="mailto:notifications@github.com">> wrote:

I checked the console log and there is no error or warning.

The exact issue:

You open a example page ( https://gist.github.com/hanneshal/9047565 ) in Chrome or FF you get an instand download. If you use Safari you get a simple white page, rendered without any errors or alerts and no alerts. If I use doc.output('dataurl'); Safari shows the PDF inline.

—
Reply to this email directly or view it on GitHub.

[hanneshal]

After some google action I found several "bug reports" according to W3C File Saver and Safari. http://www.w3.org/TR/file-writer-api/#the-filesaver-interface

It seems that the implementation in Safari is not correct or not complete.
The behavior of http://eligrey.com/demos/FileSaver.js/ is the same like jspdf.

[MrRio]

That's annoying. Perhaps we detect Safari and do something else?

[hanneshal]

Like a "shim" special for Safari?

[diegocr]

Hi there, i've downloaded Safari (5.1.7) for Windows to give it a try, testing our demo page i got a malformed PDF being generated when clicking "Download PDF", this is now fixed: c9c9c7b

So, i think that should resolve your "simple white page" issue/concern.

However, there's still the issue of the generated PDF being opened in a new window/tab rather than handled as a download when using the .save() method, and this seems to be a well know limitation of the FileSaver.js project, as pointed on their issue 12

Hence, as James suggested we may should check for Safari and do something else, Downloadify?

[jordanaustin]

@hanneshal @MrRio It is very annoying, Safari has not implemented any part of the spec that would allow us to be able to initiate an actual download. I have worked with the FileSaver library for many many hours and in fact I turned to jsPDF to specifically counteract the issue somewhat (more info in my comments here: eligrey/FileSaver.js#12).

For users who have the Acrobat plugin for Safari on the desktop they will get a new window with the PDF document loaded in the reader, and from there you can download the document. It's a huge pain, but right now I have yet to find a valid work-around.

[hanneshal]

On a Mac - Mavericks and Safari 7.0.1 the behavior is "ok" for me. You can download it with a single click inside the pdf. A hint in the docs, that the diffs to the "other ones" would be nice. I don't think that you need to put that much effort in it just because Apple says "no" to the File*** API

regards