Geolocation privacy implementation

Back when we were discussing whether to add language for what sorts of  
privacy options a UA should implement alongside the Geolocation API,  
the argument was made that this was a UI issue, and that different UAs  
would implement things differently.  Now that we have production  
Geolocation support in 4 of the major browsers (IE, where are you?), I  
thought we might take a look at how these browsers have implemented  
privacy UI.  To first order, pretty much the same way:
<http://geopriv.dreamhosters.com/w3c/w3c-geolocation-implementation.gif>

There are some small differences ("remember for this site", 24-hour  
limit), and some more major differences in how the list of authorized  
sites is managed after the initial permission is given.  But in broad  
terms, all these approaches are pretty similar.

It seems like it could be helpful to users if this group could discuss  
some of these areas where there are differences, and maybe produce a  
BCP for how they should be resolved (probably in the form of some  
privacy UI recommendations in the API spec).

Received on Tuesday, 6 July 2010 02:10:01 UTC