UX problems with Lessons comments tool & CKEditor autosave

The vast majority of views in Sakai that load the CKEditor have this editor displayed and ready to use by the time the page is fully loaded. The comments tool feature in Lessons differs (perhaps uniquely) in that the CKEditor is first loaded and then hidden before the page is fully loaded. This behavior clashes with assumptions behind how the auto-save plugin for the CKEditor behaves, particularly when alerting users that auto-saved content for a Lessons comment differs from content loaded from Sakai. An incident of this is demonstrated in “Test A” in the Test Plan.  

Another issue pertains to the different URLs expressed for a Lessons subpage when a user navigates to that subpage in different ways. The CKEditor autosave plugin currently uses the full URL for constructing a unique SaveKey for storing autosaved content. Consequently, even if the problem demonstrated in Test A is resolved, if a user has auto-saved content for the Comments tool within a subpage but later accesses the subpage in a different way than how the subpage was originally accessed when the comment in question was auto-saved, that auto-saved content will not be detected. An incident of this is demonstrated in “Test B” in the Test Plan.