Tracking bug for the geolocation part of the Content Modularization Project. The end goal should be to have a self-contained service. As part of getting rid (or greatly reducing) content/, this code should move out of content/. Most likely to device/geolocation to be consistent with what's being done for other device related APIs.
Strawman proposal, following other services that we're extracting from content:
-eliminate the dependencies in this code on other code in content/
-move remaining code in content/browser/geolocation to device/geolocation
Comment 1 by jam@chromium.org
, May 17 2016