On 5/21/13 4:45 PM, Doug Turner wrote:
The main difference is that you will get one prompt from the OS the first time you use geolocation from Firefox -- just like every other standard Mac application.
Could be a little odd, but as long as it comes up after our own permission dialog it should be ok.
I was curious if Safari was pre-cleared for this or not. Looks like it isn't -- I triggered geolocation from maps.google.com, then I got Safari's prompt for the page, and then an OS prompt regarding Safari was presented. Nice that they're playing by their own rules. :)
But, hmm... Slightly worrysome -- I clicked "don't allow", and now I can't get Safari's geolocation to work. It's own dialog comes up, but I never get the OS prompt again (even after restarting the app).
Yikes, this is crappy. The OS only asks once, and then your choice is (permanently?) stored in Preferences --> Security & Privacy --> Location Services. I had to google to find this, as Safari just silently passes on a failure to the site. I seriously wonder if we should have some UI (notification bar?) to note when Core Location fails (and send the user to a SUMO page explaining how to reenable it).
Do the Core Location APIs provide a unique error code for when the user/OS has blocked permission?
Justin _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
