Add initial version of chrome://popular-sites-internals page

chrome/browser/resources/popular_sites_internals.css

Index: chrome/browser/resources/popular_sites_internals.css
diff --git a/chrome/browser/resources/popular_sites_internals.css b/chrome/browser/resources/popular_sites_internals.css
new file mode 100644
index 0000000000000000000000000000000000000000..9c6888b8097f433d60569e84a3f0fdd22342b76c
--- /dev/null
+++ b/chrome/browser/resources/popular_sites_internals.css
@@ -0,0 +1,45 @@
+/* Copyright 2015 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. */
+
+html {
+  font-size: larger;

[Bernhard Bauer, 2015/09/11 16:00:06]

Do we really use "larger" as a value?

[Marc Treib, 2015/09/22 11:13:56]

Well, it's a valid css value. I don't know of any guidelines about using it in
Chrome, but since this an internal debugging page, I think it's fine.

[Bernhard Bauer, 2015/09/22 13:49:21]

Just because it's an internal debugging page doesn't mean that guidelines don't
apply. Basically, "larger" only makes sense together with a previous font-size
declaration, and then you could just set the absolute size (maybe as one of
"small", "large", etc. if that's how the size is defined at the top level).

[Marc Treib, 2015/09/22 14:02:22]

As I said, I don't know of any guidelines about this. The previous font-size
comes from text_defaults.css here.
But whatever - I've put in an absolute size instead.

+}
+
+#info > div {
+  width: 100%;
+}
+
+#info h2 {
+  color: rgb(74, 142, 230);
+  font-size: 100%;
+  margin-bottom: 0;
+}
+
+#info .err {
+  color: red;
+}
+
+#info .section {
+  display: inline-block;
+  margin-left: auto;
+  margin-right: auto;
+}
+
+#info .section.hidden {
+  display: none;
+}
+
+.section-details {
+  width: 100%;
+}
+
+.section-details .detail,
+.section-details .value {
+  width: 50%;
+}
+
+.section-details tr:nth-child(odd) {
+  background: rgb(239, 243, 255);
+}
+