Update UI and catch executeScript errors now shown in Canary

go-back-with-backspace/pages/options.css

Index: go-back-with-backspace/pages/options.css
diff --git a/go-back-with-backspace/pages/options.css b/go-back-with-backspace/pages/options.css
index 936a4613792c9834d1b9f4af67d80e84bc15b6cd..ff17621ba3ed74a09d725de3b5b69da369f35279 100644
--- a/go-back-with-backspace/pages/options.css
+++ b/go-back-with-backspace/pages/options.css
@@ -5,37 +5,55 @@
  */
 
 body {
-  padding: 10px;
+  background-color: white;
   direction: __MSG_@@bidi_dir__;

[Devlin, 2016/11/05 02:18:21]

This should be handled by the user's browser preference, I'd think - is it not?

[Pam (message me for reviews), 2016/11/05 04:12:56]

I'll check.

Meanwhile, I started out by following the example in
https://developer.chrome.com/extensions/i18n
That should be updated to use the better practices you suggested:
-webkit-padding-{start|end}, text-align: end, no body direction if it's not
needed. Filed as 662632.

+  margin: 0;
+  padding: 10px;
 }
 
 textarea {
+  -webkit-padding-start: 4px;
+  margin-top: 2px;
   width: 100%;
-  margin: 0;
-  padding: 0;
 }
 
-.applets {
-  padding-top: 20px;
+input {
+  margin-bottom: 20px;
+}
+
+fieldset {
+  border: solid 1px rgb(204, 204, 204);
+  border-radius: 3px;
+  padding: 4px 8px;
+}
+
+fieldset legend {
+  color: rgb(0, 51, 102);
+}
+
+.feedback-button {
+  padding: 5px 0;
+  text-align: end;
 }
 
-.whitelist {
-  padding-top: 10px;
-  padding-__MSG_@@bidi_start_edge__: 40px;
+.setting {
+  margin: 2px 0;
+}
+
+.sub-setting {
+  -webkit-margin-start: 10px;
+  margin-top: 5px;
 }
 
 .buttons {
-  padding-top: 2px;
-  padding-bottom: 1px;
-  padding-__MSG_@@bidi_start_edge__: 20px;
-  padding-__MSG_@@bidi_end_edge__: 0px;
-  text-align: __MSG_@@bidi_end_edge__;
+  -webkit-margin-end: 0;
+  -webkit-margin-start: 20px;
+  margin-bottom: 1px;
+  margin-top: 2px;
+  text-align: end;
 }
 
 #error {
   color: red;
-}
-
-#report_page {
-  float: __MSG_@@bidi_start_edge__;
+  margin: 5px 0;
 }