- From: <bugzilla@jessica.w3.org>
- Date: Thu, 31 Oct 2013 22:44:37 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23450
--- Comment #4 from Glenn Maynard <glenn@zewt.org> ---
I didn't mean that it should be possible to set the Content-Disposition header
directly. What I meant was that we should define this in terms of what
Content-Disposition does. For example, something like "user agents should
determine the preferred filename of the resource as though it was a network
request that had a Content-Disposition with a filename of .name".
This avoids this being a narrow special case for particular UIs ("save as
dialogs should use this as the default filename"), so it's clear that this
should apply everywhere a content-disposition would apply.
(It could actually be exposed as a real Content-Disposition header, eg. through
XHR, but it doesn't have to be. It's just the behavior we're looking to hook
into.)
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 31 October 2013 22:44:38 UTC