Yeah, it is. But I'm also in the US. That sometimes (read that, often) makes a difference, especially when pulling positions from WiFi network associations. When you're dealing with cell phone or mobile stuff (i.e., where the geolocation API can triangulate using cell signals or GPS), it the whole process tends to be more reliable.
You could just choose to look at it as a bonus: not many people are capable of being in two places at once! Jeremy R. Geerdes Generally Cool Guy Des Moines, IA For more information or a project quote: [email protected] If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church! On Jun 30, 2011, at 6:17 PM, kfa1983 wrote: > Quoted: "every modern browser and MSIE9". > > I like that :D > > Anyway, I'm not using the JSAPI unfortunately... Yes, I'm using W3C compliant > browsers only (mostly Chrome) and it was working perfectly until now... > > How does it work for you? Is it accurate? > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps JavaScript API v3" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-maps-js-api-v3/-/auxDWE7FomQJ. > 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=en. -- 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=en.
