We use the SCORM debug window to monitor and debug issues with Storyline content in our LMS. A recent update to some content published with v3.50.24xxx Storyline no longer shows us the debug window. We call the ShowDebugWindow() function in the browser developer tools console while we're in the sco scope of the player.
Has something changed, because we have done extensive testing over the past month using the debug window?
I think we may have had a SCORM package with bad or unseen characters in the title. It seems to be reporting fine after republishing with a cleaned title.
1 Reply
I think we may have had a SCORM package with bad or unseen characters in the title. It seems to be reporting fine after republishing with a cleaned title.
And the ShowDebugWindow() function has returned.