On Nov 18, 10:46 am, String <[email protected]> wrote:
> To do it client-side, you'd need to sniff out thebrowserand use > different code based on that. For example, iPhone's Mobile Safari does > have a built-ingeolocationAPI. So does Opera Mobile, though I don't > know if they use the *same* API. Android's "Chrome Lite" has Gears > built in. And so on. > There is W3C geolocation API draft. http://dev.w3.org/geo/api/spec-source.html More and more browsers are supporting that. E.g. Android 2.0 browser supports W3C API though it still supports Gears location API too. There is a script that makes use of Gears location or AJAX ClientLocation if W3C navigator.geolocation is not found. http://google-ajax-examples.googlecode.com/svn/trunk/whereareyou/scripts/geometa.js -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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/google-maps-js-api-v3?hl=.
