Polymer Settings Scaffold in MD-Settings

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

Index: chrome/browser/resources/settings/settings_page/settings_page_header.html
diff --git a/chrome/browser/resources/settings/settings_page/settings_page_header.html b/chrome/browser/resources/settings/settings_page/settings_page_header.html
new file mode 100644
index 0000000000000000000000000000000000000000..978c01c11de85d4dc21312a2dd04f0763800217c
--- /dev/null
+++ b/chrome/browser/resources/settings/settings_page/settings_page_header.html
@@ -0,0 +1,12 @@
+<link rel="import" href="chrome://resources/polymer/core-icon/core-icon.html">
+
+<polymer-element name="cr-settings-page-header" layout horizontal center>
+  <template>
+    <link rel="stylesheet" href="settings_page_header.css">
+    <div id="icon-container">

[Jeremy Klein, 2015/03/13 23:51:51]

nit: this should be a class.

[michaelpg, 2015/03/17 06:30:15]

I'm not sure what you mean. Do you mean we should wrap core-icon in cr-icon? I
don't know if that's necessary as it's a pretty basic building block.

[Jeremy Klein, 2015/03/17 06:38:00]

No, sorry I mean the id should be a class instead here. If it needs to be an id
for convenient js access (looks like it isn't used that way at the moment), it
should be camel-case instead of dashes.

[michaelpg, 2015/03/17 21:52:05]

Oh, haha. Yeah, it doesn't have to be an ID and it makes more sense as a class.

+      <core-icon icon="{{page.icon}}"></core-icon>
+    </div>
+    <h1>{{page.pageTitle}}</h1>
+  </template>
+  <script src="settings_page_header.js"></script>
+</polymer-element>