Add `chrome.contentSettings.location`.

chrome/common/extensions/api/content_settings.json

Index: chrome/common/extensions/api/content_settings.json
diff --git a/chrome/common/extensions/api/content_settings.json b/chrome/common/extensions/api/content_settings.json
index 5d21a7030eb98e8ce1e3d3f7e40d1f5bc9cca198..6f09fc4a49780fe1dcf2f678a08f245a1871093a 100644
--- a/chrome/common/extensions/api/content_settings.json
+++ b/chrome/common/extensions/api/content_settings.json
@@ -197,6 +197,14 @@
           {"type":"string", "enum": ["allow", "block"]}
         ]
       },
+      "location": {
+        "$ref": "ContentSetting",
+        "description": "Whether to allow Geolocation. One of <br><var>allow</var>: Allow sites to track your physical location,<br><var>block</var>: Don't allow sites to track your physical location,<br><var>ask</var>: Ask before allowing sites to track your physical location. <br>Default is <var>ask</var>.<br>The primary URL is the main-frame URL. The secondary URL is the URL of the top-level frame.",

[Bernhard Bauer, 2015/01/13 10:52:49]

This comment still doesn't make much sense. The main frame _is_ the top-level
frame, no? ;-)

[Mike West, 2015/01/13 13:00:30]

The main frame is the frame of the document whose URL is being tested. That is,
if example.com frames notexample.com, and notexample.com requests geolocation
data, notexample.com would be the "main frame", and example.com would be the
"top-level" frame.

This is consistent with the rest of the properties here, though I agree that it
could be phrased better. We should either run with "main-frame" here as well, or
change them all.

[Bernhard Bauer, 2015/01/13 23:09:37]

Not really. In other content setting types, "main-frame" does refer to the
top-level frame. For example, for plug-ins a content setting with primary URL
example.com governs whether plugins are allowed to run when example.com is
visible in the omnibox. This definition of "main frame" also matches what is
returned by RenderView::GetMainRenderFrame() et al. So if you want to use the
term "main-frame"[1] here, it should be used for the secondary URL.

[1] We should probably lose the dash here, but that's a change to make for all
content setting types in one go.

+        "value": [
+          "location",
+          {"type":"string", "enum": ["allow", "block", "ask"]}
+        ]
+      },
       "plugins": {
         "$ref": "ContentSetting",
         "description": "Whether to run plug-ins. One of<br><var>allow</var>: Run plug-ins automatically,<br><var>block</var>: Don't run plug-ins automatically. <br>Default is <var>allow</var>.<br>The primary URL is the main-frame URL. The secondary URL is not used.",