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: Mon, 17 Apr 2017 15:04:24 +0200
Message-ID: <CADnb78im8SMdfPt5-_ZHum=Pw2fyQJEAL0iHu8NBKhs3T1xkqQ@mail.gmail.com>
To: duanyao <duanyao@ustc.edu>
Cc: David Kendal <me@dpk.io>, "whatwg@whatwg.org" <whatwg@whatwg.org>, Domenic Denicola <d@domenic.me>
On Mon, Apr 17, 2017 at 2:54 PM, duanyao <duanyao@ustc.edu> wrote:
> 在 2017年04月15日 02:09, Domenic Denicola 写道:
>> file: URLs are part of the web, e.g. parsing such URLs when used in <a>
>> tags, just like gopher: URLs or mailto: URLs. The behavior once navigating
>> to file: URLs (or gopher: URLs, or mailto: URLs) is off the web, and outside
>> the scope of the WHATWG's work.
>
> This still doesn't explain why file: protocol CAN'T be part of the web (and
> inside the the scope of WHATWG).

Because it's a mechanism for addressing resources on a specific OS.
It's not a mechanism for addressing resources on the web.


-- 
https://annevankesteren.nl/
Received on Monday, 17 April 2017 13:04:57 UTC

This archive was generated by hypermail 2.3.1 : Monday, 17 April 2017 13:04:57 UTC