1. 18 Sep, 2024 2 commits
  2. 16 Sep, 2024 8 commits
  3. 12 Sep, 2024 1 commit
  4. 09 Sep, 2024 5 commits
  5. 04 Sep, 2024 9 commits
  6. 02 Sep, 2024 1 commit
  7. 28 Aug, 2024 1 commit
  8. 26 Aug, 2024 4 commits
  9. 22 Aug, 2024 1 commit
  10. 21 Aug, 2024 1 commit
    • Robert Knight's avatar
      Fix failure to fetch groups in VitalSource · ab548854
      Robert Knight authored
      Before loading groups the client waits for the main document frame to connect in
      order to be able to fetch groups associated with that frame's URL. In
      VitalSource however there is no "main frame", only the current content frame, so
      `GroupsService._loadGroupsForUserAndDocument` waited indefinitely.
      
      This failure to fetch groups did not happen on the initial launch due to a
      different bug in `GroupsService._loadGroupsForUserAndDocument`. The
      `this_store.route()` call returned `null` during startup and hence the code did
      not wait for the main frame to connect. After a subsequent login/logout however,
      the `route` call returned "sidebar" and the code did wait for the main frame.
      
      This problem also did not happen in the LMS environment because there the client
      loads a set of groups specified by our LMS app, instead of fetching groups based
      on the logged-in user and current document.
      
      Solve the first problem by using the `defaultContentFrame` method to get the
      frame instead of `mainFrame`. `defaultContentFrame` returns the main frame if
      there is one, or the first content frame that connected otherwise.
      ab548854
  11. 20 Aug, 2024 1 commit
  12. 19 Aug, 2024 6 commits