[Webkit-unassigned] [Bug 87030] New: Geolocation does not immediately make callbacks to new requests while other requests are in progress
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon May 21 10:46:19 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=87030
Summary: Geolocation does not immediately make callbacks to new
requests while other requests are in progress
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebCore Misc.
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: steveblock at google.com
CC: benjamin at webkit.org
Repro steps ...
- Start a watchPosition() request
- Wait for the success callback to be called
- Start a getCurrentPosition() request
Providing a position is obtained, the watchPosition() success callback is called as expected. When the getCurrentPosition() request is made, its success callback should be called with the same position. Instead, it is not called until an updated position is obtained.
The spec [1] states that if the location acquisition process is successful, we should invoke the success callback. In this case, when we make the getCurrentPosition() request, a successful location acquisition process is already ongoing, and I think it makes sense to use the already obtained position for the success callback. This matches the developer's expectation that a getcurrentPosition() request should be independent of any ongoing watchPosition() requests.
The problem is that GeolocationController only informs the GeolocationClient when the first request is made and the when the last request ends. It does not inform the client about new requests made while other requests are ongoing.
[1] http://www.w3.org/TR/geolocation-API/#geolocation_interface
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list