W3C home > Mailing lists > Public > public-geolocation@w3.org > March 2009

Re: PositionOptions.timeout & UserAgent permission

From: Andrei Popescu <andreip@google.com>
Date: Fri, 20 Mar 2009 14:47:35 +0000
Message-ID: <708552fb0903200747y4d383ce3v85aabfa77d0c37d7@mail.gmail.com>
To: Greg Bolsinga <bolsinga@apple.com>
Cc: Doug Turner <doug.turner@gmail.com>, public-geolocation <public-geolocation@w3.org>
On Thu, Mar 19, 2009 at 6:08 PM, Greg Bolsinga <bolsinga@apple.com> wrote:
> On Mar 19, 2009, at 4:20 AM, Andrei Popescu wrote:
>
>> On Wed, Mar 18, 2009 at 3:52 PM, Doug Turner <doug.turner@gmail.com>
>> wrote:
>>>>
>>>> On Wed, Mar 18, 2009 at 3:35 PM, Doug Turner <doug.turner@gmail.com>
>>>> wrote:
>>>>>
>>>>> however, i still think the implementations should take the timeout
>>>>> starting
>>>>> point to mean "after the user has granted permission" for many reasons,
>>>>> one
>>>>> being this can not be emulated by window.setTimeout.
>>>>
>>>> Ok...but I'm still struggling to find an example where this behavior
>>>> would be useful. Do you have a concrete example?
>>>
>>>
>>> I can not.
>>>
>>> however, i did mention the weird user interactions we get if the timeout
>>> is
>>> based on invocation time -- that is, the permission dialog could be
>>> accepted
>>> at the same time that the timeout happens.  The user would think that
>>> they
>>> just approved the request, and expect that the ua starts doing
>>> geolocation
>>> stuff.
>
> This is exactly the test case a tester of mine hit, and what inspired my
> re-thinking of the entire matter.
>
>> Ok, let's do it as you suggest. Unless anyone else objects, I will
>> update the spec and post a link to the diff.
>
> Thanks.
>

I added a Note about this:

http://dev.w3.org/geo/api/spec-source.html#timeout

The diff is http://dev.w3.org/cvsweb/geo/api/spec-source.html.diff?r1=1.48&r2=1.49&f=h

Thanks,
Andrei
Received on Friday, 20 March 2009 14:48:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:33:52 UTC