Settings Rewrite: Make a common settings-section component.

chrome/browser/resources/settings/settings_page/settings_section.html

Index: chrome/browser/resources/settings/settings_page/settings_section.html
diff --git a/chrome/browser/resources/settings/settings_page/settings_section.html b/chrome/browser/resources/settings/settings_page/settings_section.html
new file mode 100644
index 0000000000000000000000000000000000000000..ea9c0974575e147fbb564e7765b10fea0856db21
--- /dev/null
+++ b/chrome/browser/resources/settings/settings_page/settings_section.html
@@ -0,0 +1,19 @@
+<link rel="import" href="chrome://resources/polymer/v1_0/polymer/polymer.html">
+<link rel="import" href="chrome://resources/polymer/v1_0/iron-icon/iron-icon.html">
+<link rel="import" href="chrome://resources/polymer/v1_0/paper-material/paper-material.html">
+
+<dom-module id="cr-settings-section">
+  <link rel="import" type="css" href="settings_section.css">
+  <template>
+    <paper-material>
+      <div class="header">
+        <iron-icon icon="{{icon}}"></iron-icon>
+        <div class="title">{{pageTitle}}</div>

[Dan Beam, 2015/07/22 23:12:17]

if this makes someone happy I suppose that's OK and less duplicative, but I
think enforcing a hierarchy is brittle and results in lots of optional
parameters added later

just allowing each section to define their icon/title (the OPPOSITE of this) is
fine with me.

we can just do this until one of the mocks breaks these assumptions ;)

[tommycli, 2015/07/22 23:54:38]

Acknowledged.

+      </div>
+      <div class="content-container">
+        <content id="content"></content>
+      </div>
+    </paper-material>
+  </template>
+  <script src="settings_section.js"></script>
+</dom-module>