I've been chasing a bug for the last day in a browser application using the Google Gears geolocation API. For background on this API if you're unfamiliar, see http://code.google.com/apis/gears/api_geolocation.html. The relevant aspect for now is that it allows retrieval of the device's GPS coordinates in JavaScript, after asking the user's permission.
Al least, it's supposed to ask permission - but on my G1, it doesn't. The API just fails on a "permission denied" condition, without ever asking. Everything works fine on every other Gears-enabled browser I've tried: the page asks for permission, and after you grant it, the geolocation works. Interestingly, it even works on the Android SDK's emulator. Just not my G1. So I'm posting this here for two reasons. First, I'm located in the UK, so obviously my G1 is the UK version (firmware 1.1, TMI-RC9). If someone could try this with a US G1 and report the results, that might help narrow the problem down. A test on an ADP1 would also provide another data point. Or another firmware version, if anyone has one. My testing page can be found at http://gad.getpla.net/test/geobug.html You don't need to grant the page permission to read your location if you don't want to; I'm really just interested in whether or not it asks. Second, does anyone have a good idea who would own this bug? It's apparently somewhere in the interface between Gears and Chrome-Lite, but I'm not sure which side of that fence it actually comes down on. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
