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

Re: PositionOptions.timeout & UserAgent permission

From: Greg Bolsinga <bolsinga@apple.com>
Date: Thu, 19 Mar 2009 11:08:21 -0700
Cc: Doug Turner <doug.turner@gmail.com>, public-geolocation <public-geolocation@w3.org>
Message-Id: <F4D33357-3A16-4385-9800-83608ADA688F@apple.com>
To: Andrei Popescu <andreip@google.com>
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.
Received on Thursday, 19 March 2009 18:09:02 UTC

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