- From: Charles Pritchard <chuck@jumis.com>
- Date: Thu, 26 Jan 2012 16:51:47 -0800
- To: Jonas Sicking <jonas@sicking.cc>
- CC: "Tab Atkins Jr." <jackalmage@gmail.com>, Arun Ranganathan <aranganathan@mozilla.com>, "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>
On 1/26/12 4:39 PM, Jonas Sicking wrote:
> On Thu, Jan 26, 2012 at 4:25 PM, Tab Atkins Jr.<jackalmage@gmail.com> wrote:
>> On Thu, Jan 26, 2012 at 1:21 PM, Arun Ranganathan
>> <aranganathan@mozilla.com> wrote:
>>> 2. URL.createObjectURL now takes an optional boolean, following discussions on the listserv [oneTimeOnly].
>> As I argued in<http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/1520.html>,
>> we should absolutely *not* be adding more boolean arguments to the
>> platform. They should be exposed as boolean properties in an
>> dictionary. Naked bools are impossible to decipher without memorizing
>> the call signature of every function.
> I would be ok with that. We'll possibly want to add other optional
> arguments anyway, like headers
I could see: {expires: }, {name: } and {disposition: } as useful.
I could see Allow Origin CORS as something useful too, but that's
starting to go off the range.
-Charles
Received on Friday, 27 January 2012 00:52:14 UTC