Client-based geolocation missing error handling

• Component: WebKit Misc.
• Status: RESOLVED INVALID

[Mahesh Kulkarni]

GeolocationControllerClient interface missing error handling incase of unavailability of user location. 

if startUpdating() returns error from platform client listeners should be notified of POSITION_UNAVAILABLE error

[Steve Block]

Can you explain exactly what error handling is missing?

I don't think there's any need for GeolocationControllerClient::startUpdating() to return a boolean indicating success. If the client fails to start the location acquisition process, it should asynchronously call GeolocationController::errorOccurred().

The fact that GeolocationService::startUpdating() returns a boolean is awkward, as in the case of an error, it requires the Geolocation object to manage making the error callback asynchronous.

[Jarred Nicholls]

I agree with Steve.  The fact that it's client-based alone should imply that the client asynchronously informs Geolocation by calling errorOccurred(), IMHO.

[Mahesh Kulkarni]

(In reply to comment #1)
> Can you explain exactly what error handling is missing?
> 
> I don't think there's any need for GeolocationControllerClient::startUpdating() to return a boolean indicating success. If the client fails to start the location acquisition process, it should asynchronously call GeolocationController::errorOccurred().
> 
> The fact that GeolocationService::startUpdating() returns a boolean is awkward, as in the case of an error, it requires the Geolocation object to manage making the error callback asynchronous.

Makes sense. Closing the bug. Thanks Steve and Jarred.