I have a field service application written in html5/js and delivered as a cached web app in Chrome on Windows (using a cache.manifest) to ruggedized laptops that have GPS chips in them. The application uses indexeddb to store data and sends it to the server when an Internet connection is available. Works great... except that when I try to use the html5 js geolocation api to location stamp my data, Chrome refuses to return a position when the laptop does not have an Internet connection, even though it's got a perfectly good GPS chip providing a perfectly good GPS position to Windows. My expectation is that the Chrome browser ought to use the GPS chip to provide a position to the geolocation api call I'm making regardless of whether it has a good Internet connection or not. Instead, I think it's trying to talk to a Google server-side api, and then giving up.
Any ideas on how to work around this? Feels like a bug in the browser to me...
BTW, the geolocation service in other browsers running my same codebase, like Safari on iOS, provide a location using their GPS chip even when they do not have an Internet connection.
Thanks for any help.