Issue 3887 - Support bringing up the new options page with a specific tab focused

options.js

Index: options.js
===================================================================
--- a/options.js
+++ b/options.js
@@ -1126,13 +1126,18 @@
     switch (message.type)
     {
       case "app.respond":
-        if (message.action == "addSubscription")
+        switch (message.action)
         {
-          var subscription = message.args[0];
-          var dialog = E("dialog-content-predefined");
-          dialog.querySelector("h3").textContent = subscription.title || "";
-          dialog.querySelector(".url").textContent = subscription.url;
-          openDialog("predefined");
+          case "addSubscription":
+            var subscription = message.args[0];
+            var dialog = E("dialog-content-predefined");
+            dialog.querySelector("h3").textContent = subscription.title || "";
+            dialog.querySelector(".url").textContent = subscription.url;
+            openDialog("predefined");
+            break;
+          case "switchToOptionsSection":

[Thomas Greiner, 2016/04/04 12:46:36]

Detail: Is this specific to the options page? We could make this more generic to
account for a more interesting UX.

e.g. Calling it "focusSection" would put the focus on a section on the page the
message sent to and imply all of the necessary actions to achieve that such as
switching tabs, opening dialogs and highlighting sections.

Note that in the current options page the message type is called "focus-section"
so we could reuse that (and maybe rename "addSubscription" to "add-subscription"
for consistency). There it also not only switches to the tab but highlights the
section as well (something that's missing from this implementation).

[Sebastian Noack, 2016/04/05 13:32:02]

Fine with me using a more generic name that doesn't imply the options page. Any
preference: switchToSection, switchToTab, focusSection, focusTab?
This is going to change with the current rewrite of the old options page anyway,
to comply with whatever we are going to use here. As for consistency, I'd prefer
to stick to the current scheme used by the new options page.
It seems that those aren't working currently anyway. FWIW, I think just
switching to the corresponding tab is good enough. Not that we ever used those
notifications anyway (except for one test with a limited user base).

[Thomas Greiner, 2016/04/06 12:49:12]

I'd suggest "focusSection" to no limit ourselves to tabs.
Ok, that's fine.
Should be fine for now, I agree. It's something we can implement later on when
we use it in some more common feature.

[Sebastian Noack, 2016/04/06 17:38:29]

Done.

+            document.body.setAttribute("data-tab", message.args[0]);
+            break;
         }
         break;
       case "filters.respond":
@@ -1150,7 +1155,7 @@
   ext.backgroundPage.sendMessage(
   {
     type: "app.listen",
-    filter: ["addSubscription"]
+    filter: ["addSubscription", "switchToOptionsSection"]
   });
   ext.backgroundPage.sendMessage(
   {