On 12/28/09 11:51 AM, Evan Prodromou wrote:
Brion Vibber wrote:
If all browsers behaved correctly we wouldn't need an extra option,
but some don't even ask (*cough* Chromium)
Hey, so, I'm actually having a hard time confirming this. Try this
minimal page:
http://evan.prodromou.name/testlocation.html
(You can check the source to verify that I'm not doing anything evil
with your location. (Unless you count using alert() as "evil".))
I only get "no geolocation" for Chrome and Chromium on Linux.
Am I missing something? Could it be that our users that have reported
this bug on Chrome/Chromium have actually just been getting the default
location from their profiles (because their browser doesn't support
geolocation)?
I did a little more poking on this and found that our Google Gears
geolocation API shim also included another fallback shim we didn't
realize was there -- this used the Google Client APIs to do a
geolocation lookup based on IP address, but didn't prompt the user.
Chrome Mac and Linux versions for instance which include neither the
native HTML 5 location API nor Google Gears support would end up using
this, which we misinterpreted as being an overzealous lookup on Chrome's
part.
Not a bad ability to have another lookup source, but until there's an
opt-in interface we're taking it back out so the privacy controls are
predictable again.
This _should_ mean that only HTML5 & Gears-supporting browsers known to
give an opt-in prompt will be doing lookups from now on, and anyone else
will get what they listed as their public profile location.
Fix should go live on identi.ca shortly.
Thanks to everybody for your feedback and help tracking down the
unexpected behavior -- and our apologies to Chrome & Chromium developers
for jumping the gun!
-- brion vibber (brion @ status.net)
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev
