- From: Ashley Sheridan <ash@ashleysheridan.co.uk>
- Date: Mon, 02 Aug 2010 17:29:00 +0100
On Mon, 2010-08-02 at 18:09 +0200, Dennis Joachimsthaler wrote: > Ben Schwarz <ben.schwarz at gmail.com> wrote: > > > I'm really not too sure what pre-existing problem this actually solves. > > Given that a server sets the correct mime-types for a given resource, we > > know what "type" it is already. > > Yes, since we don't want to set MIME-Types. I want to be able to set > what a file actually is. Is it a file which is supposed to be shown in > the browser? Or is it an "attachment" (refering to the content-disposition > setting) > > > Setting the Content-disposition on the client side creates an annoying > > user > > experience. > > I don't think so. What would you rather have? > > <download> > (Please right click and save target as) > > or > > <download> > Which can easily be done with sever-side code. It's still annoying for the end user when things like this happen though. For example, who do you know that hasn't turned off whatever PDF browser plugin has been installed along with their Acrobat Reader? Thanks, Ash http://www.ashleysheridan.co.uk -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100802/abdd6319/attachment-0001.htm>
Received on Monday, 2 August 2010 09:29:00 UTC