Provide a small amount of padding in extension errors for the highlight border

chrome/browser/resources/extensions/extension_error.css

Index: chrome/browser/resources/extensions/extension_error.css
diff --git a/chrome/browser/resources/extensions/extension_error.css b/chrome/browser/resources/extensions/extension_error.css
index e5301f61763f62d9b10b3caf4e9f5792d9e3172c..47b1c26d22c78b7418ec35a0972ac785a2d61e60 100644
--- a/chrome/browser/resources/extensions/extension_error.css
+++ b/chrome/browser/resources/extensions/extension_error.css
@@ -45,9 +45,11 @@
 }
 
 .extension-error-metadata {
+  -webkit-margin-after: 1px;
+  -webkit-margin-before: 1px;

[Dan Beam, 2014/09/26 01:42:19]

why not margin-(bottom|top)?

[Devlin, 2014/09/27 00:33:24]

I thought the -webkit variants were encouraged for these (even for bottom and
top).  For my own edification, is there a time when we prefer one of these over
the other (excluding the obvious case of preferring start/end for most things
due to LTR vs RTL distinctions)?

(And changed to margin-bottom\top).

[Dan Beam, 2014/09/27 01:27:41]

start/end have some useful properties for LTR/RTL.  before/after aren't as clear
to me as top/bottom, imo, and sound like ::before/::after...

+  -webkit-padding-end: 1px;
   display: flex;
   flex-direction: row;
-  width: 100%;
 }
 
 .extension-error-icon {