Cleanup: Don't close single tags.

chrome/browser/resources/net_internals/capture_view.html

Index: chrome/browser/resources/net_internals/capture_view.html
diff --git a/chrome/browser/resources/net_internals/capture_view.html b/chrome/browser/resources/net_internals/capture_view.html
index a4b5f23769668c6e00d9b80738b7ed894c67525b..b9db3279f1d67b920400ec5eaf04c31a101544b7 100644
--- a/chrome/browser/resources/net_internals/capture_view.html
+++ b/chrome/browser/resources/net_internals/capture_view.html
@@ -1,15 +1,13 @@
 <div id=capture-view-tab-content class=content-box>
   <h2>Capture options</h2>
 
-  <input id=capture-view-limit-checkbox type=checkbox />
+  <input id=capture-view-limit-checkbox type=checkbox>
   <label for='capture-view-limit-checkbox'>
     Discard old data under memory pressure.
     <i>(If you capture all events for a long time, it is possible to exhaust memory and crash. Throwing out older data avoids this problem.)</i>
   </label>
 
-  <p />

[eroman, 2012/09/24 18:23:59]

FYI, removing this caused a presentation difference (it was acting as a spacer).

I'll add back something to restore the earlier look.

BTW, is there any presubmit script to prevent this style from regressing?
Cheers.

[James Hawkins, 2012/09/25 16:23:05]

Paragraphs and breaks should not be used for spacing.  CSS styling on the
relevant content is how this should be accomplished.

-
-  <input id=capture-view-byte-logging-checkbox type=checkbox />
+  <input id=capture-view-byte-logging-checkbox type=checkbox>
   <label for='capture-view-byte-logging-checkbox'>
     Include the actual bytes sent/received.
     <i>(This will result in huge log files, and can expose sensitive data)</i>