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

chrome/browser/resources/settings/advanced_page/advanced_page.html

 <link rel="import" href="chrome://resources/polymer/v1_0/polymer/polymer.html">
 <link rel="import" href="chrome://md-settings/a11y_page/a11y_page.html">
 <link rel="import" href="chrome://md-settings/downloads_page/downloads_page.html">
 <link rel="import" href="chrome://md-settings/languages_page/languages_page.html">
 <link rel="import" href="chrome://md-settings/location_page/location_page.html">
 <link rel="import" href="chrome://md-settings/privacy_page/privacy_page.html">
 <link rel="import" href="chrome://md-settings/settings_page/settings_section.html">
 <link rel="import" href="chrome://md-settings/sync_page/sync_page.html">
 
 <if expr="chromeos">
 <link rel="import" href="chrome://md-settings/date_time_page/date_time_page.html">
 </if>
 
 <dom-module id="cr-settings-advanced-page">
   <template>
 <if expr="chromeos">
     <cr-settings-section i18n-values="page-title:dateTimePageTitle"
         expand-container="{{expandContainer}}"
         current-route="[[currentRoute]]" section="dateTime">
       <cr-settings-date-time-page prefs="{{prefs}}">
       </cr-settings-date-time-page>
     </cr-settings-section>
 </if>
     <cr-settings-section i18n-values="page-title:siteSettingsLocation"
         expand-container="{{expandContainer}}"
         current-route="[[currentRoute]]" section="location">
-      <cr-settings-location-page prefs="{{prefs}}">
+      <cr-settings-location-page prefs="{{prefs}}"

[Dan Beam, 2015/10/10 01:27:39]

why would a location-page need to know that it's category is location? 

[Finnur, 2015/10/15 15:46:32]

In email and in the CL description (a reference I've now deleted, since it no
longer applies), I mentioned that I was not renaming this class in *this* CL.
The purpose was mostly to facilitate easier comparing for you. I see now that
this is causing confusion (which in turn is probably not reflecting well on my
CL, I suspect) so I decided to take the plunge and rename this class to
alleviate that confusion. I also moved this (and other classes) out of the
location_page folder and into the site_settings folder, which is probably the
natural place for this code.

+          category="[[contentSettingsTypes.GEOLOCATION]]"
+          categories="[[contentSettingsTypes]]">
       </cr-settings-location-page>
     </cr-settings-section>
 
     <cr-settings-section i18n-values="page-title:privacyPageTitle"
         expand-container="{{expandContainer}}"
         current-route="[[currentRoute]]" section="privacy">
       <cr-settings-privacy-page prefs="{{prefs}}"
         current-route="{{currentRoute}}">
       </cr-settings-privacy-page>
     </cr-settings-section>
@@ skipping 20 matching lines @@
     </cr-settings-section>
 
     <cr-settings-section i18n-values="page-title:syncPageTitle"
         expand-container="{{expandContainer}}"
         current-route="[[currentRoute]]" section="sync">
       <cr-settings-sync-page></cr-settings-sync-page>
     </cr-settings-section>
   </template>
   <script src="advanced_page.js"></script>
 </dom-module>