Extensions Docs Server: Samples search and icons

chrome/common/extensions/docs/server2/static/css/samples.css

Index: chrome/common/extensions/docs/server2/static/css/samples.css
diff --git a/chrome/common/extensions/docs/server2/static/css/samples.css b/chrome/common/extensions/docs/server2/static/css/samples.css
new file mode 100644
index 0000000000000000000000000000000000000000..f08e8223cb50587462d5def989c5215c84e8bfc8
--- /dev/null
+++ b/chrome/common/extensions/docs/server2/static/css/samples.css
@@ -0,0 +1,37 @@
+#controls {

[not at google - send to devlin, 2012/07/24 01:09:55]

general CSS comment: if you look at the page there is a lot of underlining going
on. Distracting underlining, like underneath the headers, and for each API name.

Then the links in "Filter by API" aren't underlined and it looks like a crazy
block of text.

Here's what I think: get rid of all the underlines, then see comment in the
template.

[cduvall, 2012/07/24 20:14:47]

Done. I assume all the underlining you were talking about is in the old samples
page?

+  margin: 10px 0;
+  background: #EEE;
+  padding: 10px;
+  border-radius: 10px;
+}
+
+.controlbox {
+  padding-left: 12em;
+  position: relative;
+}
+
+.controlbox strong {
+  position: absolute;

[not at google - send to devlin, 2012/07/24 01:09:55]

Yeah, really weird to be using the type of tag to do positioning. Definitely
calls for classed-spans.

Also, perhaps using a table would be more appropriate than this manual
positioning logic.

[cduvall, 2012/07/24 20:14:47]

Done.

+  left: -10px;
+  top: 2px;
+  text-align: right;
+  width: 12em;
+}
+
+.controlbox input {
+  width: 30em;
+  margin-bottom: 4px;
+}
+
+.sample {
+  position: relative;
+  padding-left: 80px;
+}
+
+img.icon {
+  position: absolute;
+  width: 64px;
+  height: 64px;
+  left: 0;
+  top: 40px;
+}