Bug 40373
| Summary: | Support only client-based Geolocation | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Steve Block <steveblock> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | abarth, ap, ddkilzer, gyuyoung.kim, joth, laszlo.gombos, luiz, sam, steveblock |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 40374, 42068, 42629, 43925, 45752, 48518, 50074, 64970, 66759, 78853 | ||
| Bug Blocks: | 41341, 43956, 52368 | ||
Steve Block
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Steve Block
*** This bug has been marked as a duplicate of bug 78853 ***