Convert SiteSettingsCategory to use the HostContentSettingsMap instead of

chrome/browser/resources/settings/site_settings/prefs_private_api.js

Index: chrome/browser/resources/settings/site_settings/prefs_private_api.js
diff --git a/chrome/browser/resources/settings/site_settings/prefs_private_api.js b/chrome/browser/resources/settings/site_settings/prefs_private_api.js
new file mode 100644
index 0000000000000000000000000000000000000000..e02b2358968e301d3cbc942e88190a4555f142cb
--- /dev/null
+++ b/chrome/browser/resources/settings/site_settings/prefs_private_api.js
@@ -0,0 +1,29 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+(function() {
+'use strict';
+
+Polymer({
+  is: 'prefs-private-api',
+
+  /**
+   * Sets the default value for a site settings category.
+   * @param {number} contentType The category to change.
+   * @param {number} defaultValue The value to set as default.
+   */
+  setDefaultValueForContentType: function(contentType, defaultValue) {
+    chrome.send('setDefaultValueForContentType', [contentType, defaultValue]);
+  },
+
+  /**
+   * Gets the default value for a site settings category.
+   * @param {number} contentType The category to change.
+   * @return {Promise}
+   */
+  getDefaultValueForContentType: function(contentType) {
+    return cr.sendWithPromise('getDefaultValueForContentType', contentType);
+  },
+});
+})();

[Finnur, 2016/02/16 15:41:04]

At first, I had a corresponding cr singleton object, much like:
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/res...

But, then I realized it looked redundant with the two functions above being so
simple, so I removed it. It may make a comeback in a future CL if there is need,
or if you think it is warranted.

[tommycli, 2016/02/17 18:18:06]

After a long discussion with dpapad, we agreed that the best way to do this type
of pattern is to make a FooBrowserProxy object like this:

https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/res...


There is no need to make a Polymer element, because the Polymer element that
calls it can just call: FooBrowserProxy.getInstance().foo().

[Finnur, 2016/02/18 20:38:17]

Done.

I'm fine with that, as long as this doesn't conflict with the consensus on the
email thread about chrome.send wrappers (meaning I'd have to rip it out and do
it differently at a later point). :)