Richard, The WHATWG mailing list is actually not an appropriate place for either this kind of e-mail (I'm not even really sure what this e-mail was supposed to be... are you an implementor?) nor your other recent e-mail (voting for a feature doesn't help in the WHATWG, all that matters is the quality of arguments and data presented).
I urge you to read the WHATWG FAQ before sending further e-mails to the list. Thanks. https://wiki.whatwg.org/wiki/FAQ If you wish to respond to this e-mail please do not cc the WHATWG list in your reply. Cheers, -- Ian Hickson On Tue, Nov 29, 2016 at 11:46 PM Richard Maher <mahe...@googlemail.com> wrote: Contact emails mahe...@gmail.com *Summary* Secure, user-sanctioned geolocation collection is currently unavailable for HTML5 Web-Apps when they are not running or in the foreground. This leaves the browser hosted applications incapable of competing with Native Apps on an even playing field. The main goal of background geolocation reporting is to all web-apps, but in particular, Gaming, Social-Network, and Fleet-Management Apps, to continue to function even if the device has gone to sleep or another App is in the foreground. Additional goals are: - Power-Saving. By using the existing ServiceWorker paradigm and flexible throttle/filter on which geolocation movements are "interesting". - Single-process (Google Play etc) to monitor all geolocation reports for all Apps before deciding if ServiceWorker(s) need to be instantiated. - Unlike Mozilla's current implementation, stalkers, estranged spouses, and marketeers will no longer be allowed to track users covertly. Here is design overview document: https://sites.google.com/a/chromium.org/dev/developers/design-documents/ ServiceWorker/TravelManagerEvent < https://www.google.com/url?q=https%3A%2F%2Fsites.google.com%2Fa%2Fchromium.org%2Fdev%2Fdevelopers%2Fdesign-documents%2Fsync%2Funified-sync-and-storage-overview&sa=D&sntz=1&usg=AFQjCNHwnrvcFIOorADSVqVKlLO-C3dOcQ > Ongoing technical constraints None. See https://w3c.github.io/ServiceWorker/#extensibility Tracking bug There is currently no top level bug. *FOR MORE PLEASE SEE: - * https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/kDq4t93zbpA