separate about page into its own page (included in chrome://chrome)

chrome/browser/resources/uber/uber.html

Index: chrome/browser/resources/uber/uber.html
diff --git a/chrome/browser/resources/uber/uber.html b/chrome/browser/resources/uber/uber.html
index 7d382784daea24d7c2b0709aaa3d02db9c17dfaa..68ae7efbb6a43b0c906d0eff348bdca7c51b3a36 100644
--- a/chrome/browser/resources/uber/uber.html
+++ b/chrome/browser/resources/uber/uber.html
@@ -21,6 +21,9 @@
   <ol>
     <li class="selected" i18n-content="settingsDisplayName"></li>
     <li i18n-content="extensionsDisplayName"></li>
+<if expr="pp_ifdef('chromeos')">
+    <li i18n-content="aboutPageDisplayName" id="aboutPageNavItem"></li>
+</if>
   </ol>
 </div>
 
@@ -32,6 +35,11 @@
 <div class="iframe-container" i18n-values="id:extensionsHost">
   <iframe src="chrome://extensions-frame/"></iframe></div>
 
+<if expr="pp_ifdef('chromeos')">
+  <div class="iframe-container" i18n-values="id:aboutPageHost">
+    <iframe src="chrome://about-page-frame/"></iframe></div>

[Dan Beam, 2012/01/09 23:05:51]

Why isn't </div> on following line?

[Evan Stade, 2012/01/09 23:31:16]

I haven't actually looked at an html style guide, if one even exists, however
I've seen this done a lot and I don't think it hurts readability. Do you?

[Dan Beam, 2012/01/09 23:53:14]

At first I thought there was no end </div> tag as it wasn't nested as I'm used
to.

[Evan Stade, 2012/01/10 04:09:45]

I dislike the idea of putting every closing tag on a new line because that will
lead to a lot of new lines. In our code, there is a lot of precedent for placing
multiple end tags on the same line, and no style guide exists to contradict it,
so I prefer to leave it this way.

+</if>
+
 </body>
 
 <script src="chrome://chrome/strings.js"></script>