Noissue - Load options on DOMContentLoaded rather than jQuery.ready

desktop-options.js

Index: desktop-options.js
===================================================================
--- a/desktop-options.js
+++ b/desktop-options.js
@@ -181,17 +181,16 @@
   });
 
   // Load recommended subscriptions
   loadRecommendations();
 
   // Show user's filters
   reloadFilters();
 }
-$(loadOptions);
 
 function convertSpecialSubscription(subscription)
 {
   for (let filter of subscription.filters)
   {
     if (whitelistedDomainRegexp.test(filter.text))
       appendToListBox("excludedDomainsBox", RegExp.$1);
     else
@@ -698,16 +697,18 @@
     else if (typeof args[i] == "function")
     {
       links[i].href = "javascript:void(0);";
       links[i].addEventListener("click", args[i], false);
     }
   }
 }
 
+document.addEventListener("DOMContentLoaded", loadOptions);
+
 ext.onMessage.addListener(message =>

[Manish Jethani, 2017/10/05 20:10:13]

By the way I notice that this listener could get called before the DOM is ready.

[Manish Jethani, 2017/10/05 20:12:34]

It won't in practice though because of the recent changes we made to
showOptions; we can ignore this.

[Sebastian Noack, 2017/10/05 20:14:47]

Unlikely, as the document isn't loaded over the network, but possible. I guess
let's ignore it until we run into any actually reproducible issue, caused by
this, in particular since the options page is eventually replaced. The new
options page might have the same theoretical race condition though.

 {
   switch (message.type)
   {
     case "app.respond":
       switch (message.action)
       {
         case "addSubscription":