I HATE sites that force downloading! I often have a 50+ MBit/sec connection and want to be able to choose between having a PDF (e.g. a invoice - all I need is the amount and the bank data) render in the browser so I can discard it after using (here: wiring the money) and not having to do: 1) download it 2) open it 3) do what I want to do 4) delete the file (which requires me to open the download folder, locate the fi…
I don't know what OS you are using, but on linux, I save all of those files to /dev/shm. Since this parks it in shared memory, once I restart my computer at some point, they will be gone. The same can be done by using a tmpfs as your default download destination and a script that cleares any file older than x days etc. I basically use two download folders: ~/Dowloads/* and /dev/shm/; the first is being used for Downl…
“Right click and save as” needs to go away
31–40 of 194 posts
Re: “Right click and save as” needs to go away
#32– Chrome, from version 14
– Firefox from version 20 (current)
– Android Browser from version 10 (current)
– Chrome for Android from version 25 (current).
Re: “Right click and save as” needs to go away
#33Re: “Right click and save as” needs to go away
#34There are already ways to force browsers to download using HTTP headers. The author says this is a "server-side solutions to front-end problem", okay. But anyways, when pages use this already, it OFTEN pisses me off, when I want to look at a PDF in browser, but the web app/page is forcing me to save it to disk and then re-open it in another app. What we _really_ need, that we _don't_ have a way to do right now -- is…
Yeah, isn't "Content-Disposition: attachment;" header exactly for this?
Re: “Right click and save as” needs to go away
#35There are already ways to force browsers to download using HTTP headers. The author says this is a "server-side solutions to front-end problem", okay. But anyways, when pages use this already, it OFTEN pisses me off, when I want to look at a PDF in browser, but the web app/page is forcing me to save it to disk and then re-open it in another app. What we _really_ need, that we _don't_ have a way to do right now -- is…
Chrome and FF PDF viewers are better, but with Acrobat it was a bag of hurt.
Also, see: saving is the more generic answer. Save and you can see it, open it and before the Chrome 'save' button you had to re-download it.
Re: “Right click and save as” needs to go away
#36What's with Chrome adding extensions to the filename? Is this behaviour specific to Chrome on Windows or standard across all platforms? The world does not revolve around windows. File extensions are optional, not mandatory, in unix land. If the site says the file is named foobar, its name is foobar not foobar.txt.
Re: “Right click and save as” needs to go away
#37Not to mention download support in browsers got WORSE over the years. All major browsers (but especially Google Chrome with its "never ask, just do it" UI attitude) need a good download manager. I strongly prefer "save as..." over the mess that the Chrome default download behaviour is.
Re: “Right click and save as” needs to go away
#38For everyone complaining that they don't want to be forced to download--just have two buttons: March Invoice: View - Download This is much clearer for the average user than a single link with hidden right click functionality. Currently clicking on a link you have no idea what you're going to get.
so would the browser be enforcing that? Or the server? Because both options are unacceptable.
Re: “Right click and save as” needs to go away
#39For everyone complaining that they don't want to be forced to download--just have two buttons: March Invoice: View - Download This is much clearer for the average user than a single link with hidden right click functionality. Currently clicking on a link you have no idea what you're going to get.
so would the browser be enforcing that? Or the server? Because both options are unacceptable.
Re: “Right click and save as” needs to go away
#40There are already ways to force browsers to download using HTTP headers. The author says this is a "server-side solutions to front-end problem", okay. But anyways, when pages use this already, it OFTEN pisses me off, when I want to look at a PDF in browser, but the web app/page is forcing me to save it to disk and then re-open it in another app. What we _really_ need, that we _don't_ have a way to do right now -- is…
Which is funny, because I absolutely loathe opening in the browser, I prefer saving it. Chrome and FF PDF viewers are better, but with Acrobat it was a bag of hurt. Also, see: saving is the more generic answer. Save and you can see it, open it and before the Chrome 'save' button you had to re-download it.