Glad to see this proposal has a new draft.
On Sat, Jul 13, 2013 at 9:31 AM, Jonas Sicking jo...@sicking.cc wrote:
Executive Summary (aka TL;DR):
Below is the mozilla proposal for a simplified filesystem API. It
contains two new abstractions, a Directory object which allows
manipulating files
On Tue, Jul 16, 2013 at 11:29 AM, Mounir Lamouri mou...@lamouri.fr wrote:
Hi,
I am not a big fan of the Directory approach of this proposal. It puts
the API between a high level, object oriented API and a low level API.
It is unfortunately not really high level because you have to use the
On Mon, Jul 15, 2013 at 11:02 PM, Kinuko Yasuda kin...@chromium.org wrote:
Glad to see this proposal has a new draft.
On Sat, Jul 13, 2013 at 9:31 AM, Jonas Sicking jo...@sicking.cc wrote:
Executive Summary (aka TL;DR):
Below is the mozilla proposal for a simplified filesystem API. It
On Mon, Jul 15, 2013 at 11:37 PM, Arun Ranganathan a...@mozilla.com wrote:
On Jul 15, 2013, at 8:01 PM, Anne van Kesteren wrote:
So exposing FormData's contents came up again.
Can you send me a pointer to that discussion, so I can plug into it?
My bad:
On Jul 16, 2013, at 8:40 AM, Anne van Kesteren wrote:
On Mon, Jul 15, 2013 at 11:37 PM, Arun Ranganathan a...@mozilla.com wrote:
On Jul 15, 2013, at 8:01 PM, Anne van Kesteren wrote:
So exposing FormData's contents came up again.
Can you send me a pointer to that discussion, so I can plug
On Tue, Jul 16, 2013 at 8:56 AM, Eric U er...@google.com wrote:
On Mon, Jul 15, 2013 at 5:58 PM, Jonas Sicking jo...@sicking.cc wrote:
On Mon, Jul 15, 2013 at 4:47 PM, Eric U er...@google.com wrote:
What's the purpose of DestinationDict? It seems redundant.
There's basically three potential
The Push API Editors would like to publish a new WD of the Push API spec
and this is a Call for Consensus to do so, using the following ED as the
basis:
https://dvcs.w3.org/hg/push/raw-file/default/index.html
Agreement to this proposal: a) indicates support for publishing a new
WD; and b)
On Tue, Jul 16, 2013 at 8:53 AM, Eric U er...@google.com wrote:
On Tue, Jul 16, 2013 at 12:32 AM, Jonas Sicking jo...@sicking.cc wrote:
On Mon, Jul 15, 2013 at 11:02 PM, Kinuko Yasuda kin...@chromium.org wrote:
Glad to see this proposal has a new draft.
On Sat, Jul 13, 2013 at 9:31 AM, Jonas
Having the full path within the filesystem removes some of the
security benefit of not allowing .., doesn't it?
There's no problem if it's just an implementation detail.
Conversely, is the
path useful if you can't use it to manipulate anything above the
current dir in the tree?
It's useful
On 7/16/2013 5:40 AM, Anne van Kesteren wrote:
On Mon, Jul 15, 2013 at 11:37 PM, Arun Ranganathan a...@mozilla.com wrote:
On Jul 15, 2013, at 8:01 PM, Anne van Kesteren wrote:
So exposing FormData's contents came up again.
Can you send me a pointer to that discussion, so I can plug into it?
On Tue, Jul 16, 2013 at 6:21 PM, Charles Pritchard ch...@jumis.com wrote:
I'd asked about using the FormData class for x-www-form-urlencoded
requests via XHR.
http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1143
That's URLQuery.
--
http://annevankesteren.nl/
On Tue, Jul 16, 2013 at 3:47 PM, Brad Hill hillb...@gmail.com wrote:
1. Changed Fetch references. The CR document referenced the WHATWG Fetch
spec in a number of places. This was problematic due to the maturity /
stability requirements of the W3C for document advancement, and I feel also
12 matches
Mail list logo
