I suspect that reloading the page is what happened. I haven't looked into how to reproduce this myself yet.
A student's attempt data shows that they started the attempt, and then at some point the timeline shows the attempt starting from scratch again, without an LTI launch happening in the intervening period. I guess that they reloaded the page, and the response was cached, with the ab-initio SCORM data. The student was using Chrome 107.
Should the SCORM API do an AJAX call to get the CMI, instead of embedding it in the page, so it has to be fetched each time the page loads?
I suspect that reloading the page is what happened. I haven't looked into how to reproduce this myself yet.
A student's attempt data shows that they started the attempt, and then at some point the timeline shows the attempt starting from scratch again, without an LTI launch happening in the intervening period. I guess that they reloaded the page, and the response was cached, with the ab-initio SCORM data. The student was using Chrome 107.
Should the SCORM API do an AJAX call to get the CMI, instead of embedding it in the page, so it has to be fetched each time the page loads?