Bug 40373 - Support only client-based Geolocation
Summary: Support only client-based Geolocation
Status: RESOLVED DUPLICATE of bug 78853
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 40374 42068 42629 43925 45752 48518 50074 64970 66759 78853
Blocks: 41341 43956 52368
  Show dependency tree / graph
 
Reported: 2010-06-09 11:27 PDT by Steve Block
Modified: 2012-05-21 10:17 PDT (History)
9 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Block 2010-06-09 11:27:44 PDT 
The original Geolocation implementation used a platform-specific GeolocationService provided in WebCore and owned by the Geolocation object. A  client-based Geolocation implementation was later added in Bug 32499.

The maintenance burden of two implementations is becoming increasingly high, particularly in the light of possible refactorings to solve b/f cache problems, discussed in Bug 40162

The client-based implementation seems to be the correct approach as it avoids the layering violations of the initial approach, so we should switch all ports to use the client-based implementation.
Comment 1 Steve Block 2012-05-21 10:17:26 PDT 

*** This bug has been marked as a duplicate of bug 78853 ***