- From: Aaron Boodman <aa@google.com>
- Date: Mon, 4 Aug 2008 11:10:48 -0700
- To: "Chris Butler" <cbutler@dash.net>
- Cc: "Andrei Popescu" <andreip@google.com>, "Shyam Habarakada" <shyamh@microsoft.com>, "Alec Berntson" <alecb@windows.microsoft.com>, "Doug Turner" <doug.turner@gmail.com>, "Chris Prince" <cprince@google.com>, public-geolocation@w3c.org
On Wed, Jul 30, 2008 at 1:28 PM, Chris Butler <cbutler@dash.net> wrote: > As you state you can use the setTimer to effectively do a timeout. To > avoid weird states you would need to be able to also store that you > already timed out somewhere and check that every time that the callback > is called. > > This would address the case that you show an error message to the user > and then you get the callback. Couldn't you just call clearWatch() after the timeout expires? - a
Received on Monday, 4 August 2008 18:12:06 UTC