Geolocation timeout parameter behaviour does not match latest version of W3C spec

[GoogleCodeExporter]

The latest version of the W3C Geolocation spec
(http://dev.w3.org/geo/api/spec-source.html) requires that in the case of a
watch, only a single callback is made per acquisition step.
- On success, the success callback is called and any timer is stopped
- On failure, the error callback is called with code POSITION_UNAVAILABLE
and any timer is stopped
- If neither of the above occurs, the error callback is called with code
TIMEOUT on timeout

Currently, Gears may make multiple error callbacks for a single watch
acquisition process - one callback per provider. If a timeout is specified,
these callbacks may then be followed by a further error callback with code
TIMEOUT on timeout.

Original issue reported on code.google.com by stevebl...@google.com on 6 Nov 2009 at 6:37

[GoogleCodeExporter]

Correction ...

The latest version of the W3C Geolocation spec (http://dev.w3.org/geo/api/spec-
source.html#geolocation_interface) requires that for a watch ...
- On success, the success callback is called and any timer is stopped
- On failure, the error callback is called with code POSITION_UNAVAILABLE
and any timer is NOT stopped
- When the timer expires, the error callback is called with code TIMEOUT

Original comment by stevebl...@google.com on 7 Dec 2009 at 1:21