Fix: 2 login-complete handlers operate in undefined orders

Author: runestonetest

runestone/activecode/js/activecode.js

@@ -2699,6 +2699,10 @@ $(document).ready(function() {
         for (k in edList) {
             edList[k].disableSaveLoad();
         }
+    } else {
+        for (k in edList) {
+            edList[k].enableSaveLoad();
+        }
     }
 
 });
@@ -2708,13 +2712,6 @@ if (typeof component_factory === 'undefined') {
 }
 component_factory['activecode'] = ACFactory.createActiveCodeFromOpts;
 
-$(document).bind("runestone:login", function() {
-    for (k in edList) {
-        if (edList.hasOwnProperty(k)) {
-            edList[k].enableSaveLoad();
-        }
-    }
-});
 
 // This seems a bit hacky and possibly brittle, but its hard to know how long it will take to
 // figure out the login/logout status of the user.  Sometimes its immediate, and sometimes its

runestone/reveal/js/reveal.js

@@ -243,13 +243,11 @@ Reveal.prototype.hideInline = function () {
 == Find the custom HTML tags and ==
 ==     execute our code on them        ==
 =================================*/
-$(document).ready(function () {
+
+$(document).bind("runestone:login-complete",function () {
     $("[data-component=reveal]").each(function (index) {
         RevealList[this.id] = new Reveal({"orig": this});
     });
-});
-
-$(document).bind("runestone:login-complete",function () {
     if (eBookConfig.isInstructor) {
         for (const divid of Object.keys(RevealList)) {
             if (RevealList[divid].instructorOnly) {