Flesh out the location-page class to make it more general.

chrome/browser/resources/settings/advanced_page/advanced_page.js

Index: chrome/browser/resources/settings/advanced_page/advanced_page.js
diff --git a/chrome/browser/resources/settings/advanced_page/advanced_page.js b/chrome/browser/resources/settings/advanced_page/advanced_page.js
index 0943c0dd85da65f4a34129232fc8837b89c40e15..7dd61550384566655889723865ed2f9f9c1509fc 100644
--- a/chrome/browser/resources/settings/advanced_page/advanced_page.js
+++ b/chrome/browser/resources/settings/advanced_page/advanced_page.js
@@ -38,4 +38,9 @@ Polymer({
       notify: true,
     },
   },
+
+  ready: function() {
+    this.$.locationCategory.category =

[Dan Beam, 2015/10/19 07:18:05]

why wouldn't the location category itself do this?

[Finnur, 2015/10/19 13:53:58]

I'm not sure I follow. Remember... there is no location category anymore, only a
general purpose class that can display any category we want, and it needs to be
told which category to display.  I would prefer not to do it exactly like this,
and instead tell it in HTML, through a property on the HTML, such as:

   category="{{siteSettings.ContentSettingsTypes.GEOLOCATION}}"

... but as we've established, it is not clear how to do that.

+        siteSettings.ContentSettingsTypes.GEOLOCATION;
+  },
 });