Re: Drop lastPosition from Geolocation?

On Tue, Nov 18, 2008 at 9:38 AM, Doug Turner <doug.turner@gmail.com> wrote:
> It is my position that we should not have synchronous API because building a
> security UI around such a system doesn't work.  This was the core reason I
> suggested dropping lastPosition.

If the app doesn't have permission to use the Goelocation API, then
just return null. The next thing the developer will probably try to do
with be to call getCurrentPosition(), which will trigger the UI.

>From the developer's point of view the difference between "there is no
last known position" and "there is no last known position because you
don't have access to position information" is not really relevant, is
it?

- a