Update UI and catch executeScript errors now shown in Canary

go-back-with-backspace/_locales/en/messages.json

Index: go-back-with-backspace/_locales/en/messages.json
diff --git a/go-back-with-backspace/_locales/en/messages.json b/go-back-with-backspace/_locales/en/messages.json
index 481193a4b90b594c41de0e01f9432b65c01471d4..a403ed02afa4a7d8c903c903956f60b29b5e0e33 100644
--- a/go-back-with-backspace/_locales/en/messages.json
+++ b/go-back-with-backspace/_locales/en/messages.json
@@ -11,20 +11,24 @@
     "message": "Go Back With Backspace Options",
     "description": "Used in the page title and top heading of the options page."
   },
+  "optionsAppletGroup": {
+    "message": "Applets",
+    "description": "Label for the group of settings that control this extension's behavior in embedded applets (Flash, etc.)"
+  },
   "optionsBlacklist": {
-    "message": "Backspace should never navigate back on these pages (one per line):",
+    "message": "Backspace should never go back on these pages (one per line):",
     "description": "Heading for the text entry box in which the user enters a list of pages on which the backspace extension should never go back."
   },
   "optionsAppletCheckbox": {
-    "message": "Backspace should also not navigate back in embedded applets (Flash, Java, etc.).",
+    "message": "Backspace should not go back in applets (Flash, Java, PDF, and certain chat tools).",
     "description": "Label for a checkbox indicating whether the extension should go back when focus is in embedded content such as a Java or Flash applet."
   },
   "optionsWhitelist": {
-    "message": "But even in an embedded applet, backspace should navigate back on these pages:",
+    "message": "Even in an applet, backspace should go back on these pages:",
     "description": "Heading for the text entry box in which the user enters a list of pages on which the backspace extension should go back even when focus is in embedded content."
   },
   "optionsSave": {
-    "message": "Done",
+    "message": "OK",
     "description": "Label for the button that saves settings and closes the dialog."
   },
   "optionsCancel": {
@@ -46,7 +50,7 @@
     }
   },
   "popupDisallowedURL": {
-    "message": "The extension is unable to work on this page.",
+    "message": "Extensions prohibited on this page.",
     "description": "Status message shown in the popup when the current page is one of the special pages on which extensions are prohibited."
   },
   "popupFileURL": {
@@ -54,11 +58,11 @@
     "description": "Text of a link shown in the popup when the current page is a file:// URL, whether or not the extension currently has access to file:// URLs. The link leads to chrome://extensions."
   },
   "popupAddBlacklist": {
-    "message": "Never go back on this page",
+    "message": "Disable on this page",
     "description": "Label for the button in the popup that adds the current pageto a blacklist, on which the extension will never navigate back."
   },
   "popupRemoveBlacklist": {
-    "message": "Start going back from this page again",
+    "message": "Enable on this page",
     "description": "Label for the button in the popup that removes the current page from the list that controls when the extension won't navigate back from a page at all."
   },
   "popupStatusSaved": {
@@ -89,7 +93,7 @@
   },
   "reportBody": {
     "message": "Is something not working properly? A feature you'd like to see in this extension? Let us know! (We won't be able to respond to every piece of feedback individually, but we appreciate your time and thoughts.)",
-    "description": "Initial body of the feedback email created by the 'Send feedback' button in places where there is no relevant URL (e.g., the installation notes page)."
+    "description": "Initial body of the feedback email created by the 'Send feedback' button in places where there is no relevant URL (e.g., the options page)."
   },
   "reportBodyWithURL": {
     "message": "The extension doesn't do the right thing on the page at\n$URL$.\n\nAdd any details below. Which part of the page doesn't work properly? (We won't be able to respond to every piece of feedback individually, but we appreciate your time and thoughts.)",