12012-03-29 Mark Pilgrim <pilgrim@chromium.org>
2
3 GEOLOCATION should be implemented as Page Supplement
4 https://bugs.webkit.org/show_bug.cgi?id=82228
5
6 Reviewed by NOBODY (OOPS!).
7
8 Geolocation now uses the Supplement interface instead of
9 keeping an instance variable on Page. This allows us to
10 remove all geolocation-related functions, variables, and
11 ifdefs out of Page and into Modules/geolocation/.
12
13 * Modules/geolocation/Geolocation.cpp:
14 (WebCore::Geolocation::stop):
15 (WebCore::Geolocation::lastPosition):
16 (WebCore::Geolocation::requestPermission):
17 (WebCore::Geolocation::startUpdating):
18 (WebCore::Geolocation::stopUpdating):
19 * Modules/geolocation/Geolocation.h:
20 (WebCore):
21 * Modules/geolocation/GeolocationController.cpp:
22 (WebCore::GeolocationController::supplementName):
23 (WebCore):
24 (WebCore::provideGeolocationTo):
25 * Modules/geolocation/GeolocationController.h:
26 (GeolocationController):
27 (WebCore::GeolocationController::from):
28 * WebCore.exp.in:
29 * page/GeolocationClient.h:
30 (WebCore):
31 (GeolocationClient):
32 * page/Page.cpp:
33 (WebCore::Page::Page):
34 (WebCore::Page::PageClients::PageClients):
35 * page/Page.h:
36 (WebCore):
37 (PageClients):
38 (Page):
39