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

Re: PositionOptions.timeout & UserAgent permission

From: Doug Turner <doug.turner@gmail.com>
Date: Wed, 18 Mar 2009 08:35:22 -0700
Cc: Andrei Popescu <andreip@google.com>, Greg Bolsinga <bolsinga@apple.com>, public-geolocation <public-geolocation@w3.org>
Message-Id: <ED5DB874-8B92-4ED9-A344-308C1E58468B@gmail.com>
To: Doug Turner <doug.turner@gmail.com>
okay, after sleeping on this, I disagree with myself.  :-)

If the "timeout" attribute starting point is measured from when  
watchPosition or getCurrentPosition is invoked, then what we are  
talking about is basically what window.setTimeout can currently do in  
conjunction with this spec.  timeout would effectively be a connivence  
for developers.  It reduces the amount of code a developer would have  
to write, and I am all for that.

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.

Doug



On Mar 17, 2009, at 10:50 PM, Doug Turner wrote:

> is there a use case we have that can't be implemented with  
> window.setTimeout()?  If not, i propose to remove it.
>
> Doug
>
>
> On Mar 17, 2009, at 4:18 AM, Andrei Popescu wrote:
>
>> What exactly doesn't make sense? Anyway, should we just remove  
>> timeout
>> altogether? I'd be ok with that.
>
Received on Wednesday, 18 March 2009 15:36:20 UTC

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