- From: Doug Turner <dougt@dougt.org>
- Date: Thu, 8 Jul 2010 10:22:48 -0700
- To: Marcos Caceres <marcosc@opera.com>
- Cc: "Richard L. Barnes" <rbarnes@bbn.com>, Angel Machín <angel.machin@gmail.com>, public-geolocation <public-geolocation@w3.org>, Thomas Roessler <tlr@w3.org>
I thought that specific UI implementations was out of scope in this WG. Doug On Jul 7, 2010, at 11:54 PM, Marcos Caceres wrote: > A colleague at Opera suggested that perhaps we could look at the "Web Security Context: User Interface Guidelines" for inspiration on what a BCP document for Geolocation UI guidelines could look like. There is certainly a degree of overlap between [1] and what we have been discussing. See, for example, the section on indicators. > > Thoughts? > > [1] http://www.w3.org/TR/2010/PR-wsc-ui-20100622/ > > On 7/6/10 1:58 PM, Marcos Caceres wrote: >> >> >> On 7/6/10 1:27 PM, Richard L. Barnes wrote: >>> Thanks for that contribution. As far as iOS, I haven't tested version >>> 4, but as of version 3, there was a similar allow/deny, but it >>> automatically remembered, with no way to revoke. >>> >> >> FYI, I wrote a blog post a few weeks ago about "Privacy issues in Mobile >> Safari on iPhone OS 3.2". >> >> http://datadriven.com.au/2010/06/privacy-issues-in-mobile-safari-on-iphone-os-3-0/ >> >> >> >>> On Jul 6, 2010, at 4:49 AM, Angel Machín wrote: >>> >>>> Hi Richard, >>>> >>>> On Tue, Jul 6, 2010 at 4:09 AM, Richard L. Barnes <rbarnes@bbn.com> >>>> wrote: >>>>> 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). >>>>> >>>> >>>> I have tested the web app in Android, I am attaching a screen snapshot. >>>> >>>> Regards, >>>> Angel >>>> <_android_geo.png> >>> >>> >> > > -- > Marcos Caceres > Opera Software >
Received on Thursday, 8 July 2010 17:23:25 UTC