-
Notifications
You must be signed in to change notification settings - Fork 21
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
On Safari the keyring backup file opens in a new tab #97
Comments
related issue from a Filesaver lib we use, eligrey/FileSaver.js#129 |
Unfortunately I can only test from windows and linux, no mac os here |
It seems we can't get this fixed for iOS && Safari + those browsers lack some other features such as providing file names to files generated entirely in browser I would not like to pass backup file to the server just to allow user to download them cross platform it contains very sensitive information(encrypted with account password tho). We could probably give user a warning that he should copy/paste this file and save in a good place |
this is on @pzduniak side - he needs to set the HTTP header of the file he's sending. otherwise safari will just see it as another text file.
or in html5, you can use
To force the browser to download the file. note the download attribute. more info here http://stackoverflow.com/questions/5192917/force-download-through-js-or-query |
o_O @piggyslasher |
well - then you can use the
|
we don't have href ;) |
can you point me to the code that does this? i think i might have a solution. needs some trial and error. |
just make a search for saveAs calls |
the easiest place to test is settings, js/AppLavaboom/controllers/ctrlSettingsSecurity.js |
Status? |
5e7004a the file is downloaded and saved as 'unknown' in safari, with no extension. its the closest thing i got to saving the file. its a known issue and apple doesnt plan to fix it anytime soon. There is one more way using FileSystem api but I need to do more research on this. We can either
|
fixed with 0a7af34 |
No download at all
Safari Version 8.0.3 (10600.3.18)
The text was updated successfully, but these errors were encountered: