c***@googlecode.com
2016-02-17 00:13:50 UTC
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
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
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.