W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2017

Re: [whatwg] Accessing local files with JavaScript portably and securely

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 19 Apr 2017 10:09:59 +0200
Message-ID: <CADnb78jFV8rhwA-=D1ty2+Gw4SxfP2+E5QFR9OOpt9o=rQJ0OQ@mail.gmail.com>
To: duanyao <duanyao@ustc.edu>
Cc: WHATWG <whatwg@lists.whatwg.org>, Ashley Sheridan <ash@ashleysheridan.co.uk>, Ian Hickson <ian@hixie.ch>, Roger H├ągensen <rh_whatwg@skuldwyrm.no>
On Wed, Apr 19, 2017 at 5:45 AM, duanyao <duanyao@ustc.edu> wrote:
> These have been a lot of discussion on that in this thread. Do you think writing a more formal document would be helpful?

Perhaps. Fundamentally, I don't think you've made a compelling enough
case for folks to become interested and wanting to work in this space
and help you solve your problem. You've also have been fairly
dismissive of the alternative points of view, such as the web being
fundamentally linked to HTTP and that distributing (offline)
applications over HTTP is the goal. That might make folks less
compelled to engage with you.

I suspect no browser, and I'm pretty certain about Mozilla since I
work there, is interested in furthering file URLs. Most new operating
systems abstract away the file system and the web as browsers see it
has always done that. There's ways to pull files in, but there's not
much use for letting applications write them out again (other than
downloads, which are quite a bit different).

Received on Wednesday, 19 April 2017 08:10:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 19 April 2017 08:10:32 UTC