MD Settings: Certificate manager, CA edit trust dialog.

chrome/browser/resources/settings/certificate_manager_page/certificate_manager_page.js

Index: chrome/browser/resources/settings/certificate_manager_page/certificate_manager_page.js
diff --git a/chrome/browser/resources/settings/certificate_manager_page/certificate_manager_page.js b/chrome/browser/resources/settings/certificate_manager_page/certificate_manager_page.js
index 61ca5014f9c57e55a01600a964f2213874ce3591..889e7276712987b411a4afb099828b3361a1c9b5 100644
--- a/chrome/browser/resources/settings/certificate_manager_page/certificate_manager_page.js
+++ b/chrome/browser/resources/settings/certificate_manager_page/certificate_manager_page.js
@@ -6,26 +6,7 @@
  * @fileoverview
  * 'settings-certificate-manager-page' is the settings page containing SSL
  * certificate settings.
- *
- * Example:
- *
- *    <iron-animated-pages>
- *      <settings-certificate-manager-page prefs="{{prefs}}">
- *      </settings-certificate-manager-page>
- *      ... other pages ...
- *    </iron-animated-pages>

[Dan Beam, 2016/03/09 21:46:38]

note: when I removed all @group and @element tags, I left examples and the weird

@fileoverview
description on next line

I would recommend you gain consensus with the settings team first before
departing from consistency

[dpapad, 2016/03/09 22:33:56]

Reverted this, and started a thread to figure out if there is consensus.

  */
 Polymer({
   is: 'settings-certificate-manager-page',
-
-  properties: {
-    /**
-     * Preferences state.
-     * TODO(dschuyler) check whether this is necessary.
-     */
-    prefs: {
-      type: Object,
-      notify: true,
-    },
-  },
 });