- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sun, 17 Mar 2013 12:46:37 +0100
- To: Jonas Sicking <jonas@sicking.cc>
- Cc: WHAT Working Group <whatwg@whatwg.org>
On 2013-03-17 02:49, Jonas Sicking wrote: > It's currently unclear what to do if a page contains markup like <a > href="page.txt" download="A.txt"> if the resource at audio.wav > responds with either > > 1) Content-Disposition: inline > 2) Content-Disposition: inline; filename="B.txt" > 3) Content-Disposition: attachment; filename="B.txt" > > People generally seem to have a harder time with getting header data > right, than getting markup right, and so I think that in all cases we > should display the "save as" dialog (or display equivalent download > UI) and suggest the filename "A.txt". I agree that people have problems getting headers right, but in all the cases above, it seems they have set the header on purpose, no? My recollection was that a/@download was mainly added for cases where the header field couldn't be set at all... > ... Best regards, Julian
Received on Sunday, 17 March 2013 11:47:05 UTC