On Mon, Sep 29, 2014 at 12:19 PM, Dale Harvey <[email protected]> wrote: >> There's a host of problems when you're using file URLs. > > pun intended? :)
Heh. (Note that file URLs apparently count as authenticated origins. Which makes sense.) > But I agree, for a long time developing off file:/// is pretty much > impossible and developers are now required to start a server in order to > build or use their entirely offline completely unconnected application, is > it really a surprise that noone is building offline capable web apps? I hope the reason for that is that our solution for offline has been bad thus far. > 'have > an option / extention' is a weak workaround that puts the onus on often the > user(!) and the developer to be able to work around restrictions in the base > platform that shouldnt exist in the first place. I'd like to think we have restrictions for a reason, although the reason is not always great (e.g. compatibility with deployed content is a rather annoying one). > Similiarly with gUM, bluetooth, serial ports and tcp socket apis all > enabling more peer to peer (and offline capable) it seems entirely the wrong > approach to have the functionality of the base platform restricted to a > single end transport mode. I'm not sure what you mean by this. The more personal applications are, the more reason there is to deliver them over TLS. Unless you talk about some alternate way of distributing them? -- https://annevankesteren.nl/ _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
