Issue 587248 in chromium: Background GPS tracking support

[c***@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Pri-2 Via-Wizard Type-Feature OS-Android

New issue 587248 by ***@googlemail.com: Background GPS tracking support
https://code.google.com/p/chromium/issues/detail?id=587248

Steps to reproduce the problem:
Neither the current Navigator.geoLocation.watchPosition()
https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/watchPosition
or the proposed GeoFencing API https://www.w3.org/TR/geofencing/ are
capable of delivering the functionality required by Fleet-Management,
Social-Networking, Gaming, and Risk-management web-apps today.

What is the expected behavior?
WatchPosition() no longer functions in the background (See:
https://code.google.com/p/chromium/issues/detail?id=506435 for earlier
discussions)
The proposed client-device-centric and heuristically challenged GeoFencing
standard is incapable of providing what myopia-free server-based
geofencinbg can do with dynamic fencing and the complete picture of all the
players, people, trucks, pizzas.

What went wrong?
The Chromium GeoFence implementation has floundered: -
https://code.google.com/p/chromium/issues/detail?id=383125

WatchPosition can be simulated by throwing a 5m geofence around the current
position and when a "leave" event is fired then simply drop and re-create
the fence around new position.

Just the proposed restrictions on the GeoFence API that I know about: -
1) Maximum number of geofences
2) Only circular geofences
3) Maximum area of a geofence
4) Minimum area of a geofence
5) (Soon to be?) Cannot create a geofence in a service worker. At least
around current location.
6) Fat Client, localized, geofence processing
7) A technology born of a time when Java was king and batteries were the
size of a brick and lasted just 2 hours.

Did this work before? Yes Before
https://code.google.com/p/chromium/issues/detail?id=112938

Chrome version: 48 Channel: stable
OS Version: All
Flash Version:

I will detail my proposed solution next.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #2 on issue 587248 by ***@googlemail.com: Background GPS
tracking support
https://code.google.com/p/chromium/issues/detail?id=587248

Other Options: -
4) When the device goes to sleep when a Web App is still watching GPS, or
simply backgrounds or minimizes a device-tracker, it should make a sound
and or vibrate as a non-visual cue that tracking is ongoing?
5) When a device is reawakened or a device-tracking app is brought back to
the foreground, then a notification must be sent to the user "This App
continued to monitor your location in the background". The "Settings" icon
on the message could facilitate "Prevent this app from tracking in the
background" Forever/Just once.
6) Like the Push API the default must be DO NOT track in the background. If
the user chooses the individual APP settings then they can turn it on?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Updates:
Status: Available
Cc: ***@chromium.org

Comment #3 on issue 587248 by ***@chromium.org: Background GPS
tracking support
https://code.google.com/p/chromium/issues/detail?id=587248

(No comment was entered for this change.)
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Updates:
Status: Duplicate
Mergedinto: 383125

Comment #4 on issue 587248 by ***@chromium.org: Background GPS
tracking support
https://code.google.com/p/chromium/issues/detail?id=587248

This functionality really falls under the umbrella of geofencing, and hence
is a duplicate of issue 383125.

I notice that your proposal [1] to the geolocation working group was not
met with much enthusiasm, much the way it went with earlier similar
proposals. It looks to me like there are no browser vendors prioritizing
this functionality right now. Perhaps they do not agree that the use cases
are compelling and common enough, or perhaps the resource consumption,
privacy, and security issues are considered too severe.

[1]
https://lists.w3.org/Archives/Public/public-geolocation/2016Feb/0016.html
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings