From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Patrick Dark
> I can't see this being addressed. The only good reason to distribute an
> application this way is because you want it to be confidential and there's no
> incentive to accommodate what one might call "walled
On 11 Apr 2017, at 12:55, Patrick Dark
wrote:
> I can't see this being addressed. The only good reason to distribute
> an application this way is because you want it to be confidential and
> there's no incentive to accommodate what one might call "walled
David Kendal 於 4/11/2017 11:46 AM 寫道:
On 11 Apr 2017, at 17:01, Domenic Denicola wrote:
Bingo. This mailing list is for developing technology for the world
wide web, not for peoples' local computers.
The World Wide Web includes peoples' own computers. file:// is a URI
scheme
Domenic Denicola schrieb am Di., 11. Apr. 2017 um 18:01 Uhr:
> From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of
> Patrick Dark
>
> Bingo. This mailing list is for developing technology for the world wide
> web, not for peoples' local computers.
>
Doesn't that
On 11 April 2017 at 18:01, Domenic Denicola wrote:
> From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of
> Patrick Dark
>
> > I can't see this being addressed. The only good reason to distribute an
> application this way is because you want it to be confidential
On 11 Apr 2017, at 17:01, Domenic Denicola wrote:
> Bingo. This mailing list is for developing technology for the world
> wide web, not for peoples' local computers.
The World Wide Web includes peoples' own computers. file:// is a URI
scheme for exactly that reason. Every
On 2017-04-11 Patrick Dark wrote:
> Jan Tosovsky 2017-04-10 wrote:
> > > On 2017-04-09 David Kendal wrote:
> > >
> > > ... there are many possible uses for local static files
> > > accessing other local static files: the one I have in mind
> > > is shipping static files on CD-ROM or USB stick...
Dear all:
I agree with the need to consider file:// ( or at least re-consider the
missing functionality) applicable to exec files / directories with HTML
documents, stored on physical devices ( like USBs or CD-DVDs), even it
might sound uselessness in the _cloudy_ times we live.
This HTML
We should be aware of the security risks when recommand a "simple web
server".
* Most (if not all) simple web servers don't block access from non-local
hosts by default,
which can leak users' files. Although your firewall can block them
for you, users do need unblock
non-local hosts
I see that https://xhr.spec.whatwg.org/ already defines ProgressEvent
for XMLHttpRequest.
Would it be possible to add "progress", "load", etc. events to normal
form elements, too? Basically, I would like to do
form.addEventListener('progress', function (e) {...})
and if the end user hits the
Patrick Dark schrieb am Di., 11.
Apr. 2017 um 13:55 Uhr:
> [...] The only good reason to distribute an application this way is
> because you want it to be confidential [...]
>
Another use-case would be to develop a HTML app that does not require
internet
On Tue, Apr 11, 2017 at 2:44 PM, Mikko Rantalainen
wrote:
> I see that https://xhr.spec.whatwg.org/ already defines ProgressEvent
> for XMLHttpRequest.
>
> Would it be possible to add "progress", "load", etc. events to normal
> form elements, too? Basically, I would
David Kendal 於 4/9/2017 4:51 AM 寫道:
This is a shame because there are many possible uses for local static
files accessing other local static files: the one I have in mind is
shipping static files on CD-ROM or USB stick, but there is also the more
obvious (and probably more common) use of local
Jan Tosovsky 於 4/10/2017 5:38 PM 寫道:
On 2017-04-10 David Kendal wrote:
On 2017-04-09 Jan Tosovsky wrote:
On 2017-04-09 David Kendal wrote:
... there are many possible uses for local static files accessing
other local static files: the one I have in mind is shipping static
files on CD-ROM or
14 matches
Mail list logo