Re: [whatwg] Firebase Cloud Messaging (FCM) blows the W3C/IETF Success Prevention Depts out of the water!

Please follow the WHATWG code of conduct when posting to this list: https://wiki.whatwg.org/wiki/Code_of_Conduct. In particular, I believe this message violates: - Please be kind and courteous. There's no need to be mean or rude. - Respect that people have differences of opinion and that

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

在 2017年04月19日 02:23, Ian Hickson 写道: The main thing that seems to be missing from this thread is any commitment from any browser vendors to actually support any changes in this space. Yes, and I had been pessimistic about that even before I join this thread. Actually I join the discussion

Re: [whatwg] Firebase Cloud Messaging (FCM) blows the W3C/IETF Success Prevention Depts out of the water!

Hopefully the quoting below is legible: - -Original Message- From: Richard's Hotmail [mailto:maher...@hotmail.com] Sent: Wednesday, April 19, 2017 7:09 AM To: 'whatwg@lists.whatwg.org' Subject: Re: [whatwg] Firebase Cloud Messaging (FCM) blows the W3C/IETF Success Prevention Depts out of

Re: [whatwg] Firebase Cloud Messaging (FCM) blows the W3C/IETF Success Prevention Depts out of the water!

On Tue, Mar 28, 2017 at 9:30 AM, Roger Hågensen > wrote: On 2017-03-27 05:50, Richard Maher wrote: Broadcast Messaging and Topic Based subscription is now available to your WebApp just like native Apps thanks to FCM.

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

> If the browser vendors feel like this is out of scope for their product, > then spending the (quite extensive) > effort to design a solution will be wasted. I > wouldn't want anyone on this > list to feel their time is wasted. I also do not like to see W3C’s valuable time continually wasted

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

On Tue, Apr 18, 2017 at 3:36 PM Richard Maher wrote: > > The main thing that seems to be missing from this thread is any > commitment > > from any browser vendors to actually support any changes in this space. > > It has been my experience that browser vendors, more often

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

> The main thing that seems to be missing from this thread is any commitment > from any browser vendors to actually support any changes in this space. It has been my experience that browser vendors, more often than not, require at least a (proposed) standard before they will consider

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

The main thing that seems to be missing from this thread is any commitment from any browser vendors to actually support any changes in this space. I would recommend the following steps for anyone hoping to push changes to Web specifications on this topic: - Approach Web browser vendors privately,

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

在 2017年04月18日 19:27, Ashley Sheridan 写道: On 18 April 2017 12:18:57 BST, duanyao wrote: 在 2017年04月18日 18:52, Ashley Sheridan 写道: Maybe no. "files" is a generic word, so if you make every "xxx_files/" folders magical, it's quite possible that there are folders happen to

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

在 2017年04月18日 19:27, Ashley Sheridan 写道: On 18 April 2017 12:18:57 BST, duanyao wrote: 在 2017年04月18日 18:52, Ashley Sheridan 写道: Maybe no. "files" is a generic word, so if you make every "xxx_files/" folders magical, it's quite possible that there are folders happen to

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

On 18 April 2017 12:18:57 BST, duanyao wrote: >在 2017年04月18日 18:52, Ashley Sheridan 写道: >> >>> Maybe no. "files" is a generic word, so if you make every >"xxx_files/" >>> folders magical, it's quite possible that there are folders happen >to >>> ends with "_files" but are not

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

在 2017年04月18日 18:52, Ashley Sheridan 写道: Maybe no. "files" is a generic word, so if you make every "xxx_files/" folders magical, it's quite possible that there are folders happen to ends with "_files" but are not intented to be local web apps. If you require a `xxx.html` to make "xxx_files/"

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

>Maybe no. "files" is a generic word, so if you make every "xxx_files/" >folders magical, it's quite possible that there are folders happen to >ends with "_files" but are not intented to be local web apps. If you >require a `xxx.html` to make "xxx_files/" magical, it is a little >awkward and

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

在 2017年04月18日 16:08, Anne van Kesteren 写道: On Tue, Apr 18, 2017 at 9:57 AM, Roger Hågensen wrote: Searching Google for "offline webapp discussion group" turns up https://www.w3.org/wiki/Offline_web_applications_workshop and that's sadly from 2011. There is

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

在 2017年04月18日 16:09, Roger Hågensen 写道: On 2017-04-17 15:22, duanyao wrote: This can handle multipage fine as well. Anything in the folder test.html_files is considered sandboxed under test.html The problem is, what if users open `test_files\page2.html`or `test_files\page3.html`directly? Can

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

On Tue, Apr 18, 2017 at 10:25 AM, Roger Hågensen wrote: > On 2017-04-18 10:08, Anne van Kesteren wrote: >> Right, those are about making applications distributed over HTTPS work >> when the user is not connected. That idea doesn't necessitate file >> URLs and we're still

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

On 2017-04-18 10:08, Anne van Kesteren wrote: There is https://www.w3.org/TR/offline-webapps/ Right, those are about making applications distributed over HTTPS work when the user is not connected. That idea doesn't necessitate file URLs and we're still working towards that ideal with Fetch,

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

On 2017-04-17 15:22, duanyao wrote: This can handle multipage fine as well. Anything in the folder test.html_files is considered sandboxed under test.html The problem is, what if users open `test_files\page2.html`or `test_files\page3.html`directly? Can they access `test_files\config.json`? This

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

On Tue, Apr 18, 2017 at 9:57 AM, Roger Hågensen wrote: > Searching Google for "offline webapp discussion group" turns up > https://www.w3.org/wiki/Offline_web_applications_workshop > and that's sadly from 2011. > > There is https://www.w3.org/TR/offline-webapps/ Right,

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

On 2017-04-17 19:19, duanyao wrote: There are always incompatibilities between browsers, and even once standardized feature can be deprecated/removed in future, e.g. `window.showModalDialog()`, `` and ``. This happens rarely and when it happens it's a very considered decision involving lots of