Enable the Content Interface to remember which accordions are open

[djplaner]

Problem

With a complex accordion interface the current state of the accordions can be a complex process to recreate. Which is what uses have to currently do if they navigate away. Negative feedback from the Media Law students.

Proposed solution

Have the Content Interface use localstorage to remember the state of the accordions.

[djplaner]

Currently one of the last things CI does is check to see if a URL parameter has been passed specifying which accordion to open.

If there is one, we would want to ignore (and update localStorage).

If there isn't one, that's when we'd want to open the contents of localStorage if there is one.

To do

• [x] Identify when to change which accordion to open based on localStorage
• [x] Identify when to update localStorage
• [x] figure out how to generate unique key for the current page - just use the URL
• [x] set localStorage
• [x] modify which accordion is open
• [x] Figure out how to identify/restore the correct accordion
  • the element id isn't cutting it (at least not simple numeric matching - ui-id-7 == 7th accordion
  • working for heading 1, but not heading 2
• [x] Test on Blackboard
• [x] Documentation
• [x] Announce feature
• [x] Go live.