We started getting javascript errors recently. In Chrome, Firefox or latest IE it works well, but in IE11 (Win7, Win8) it gives an error "Assignment to read-only properties is not allowed in strict mode" in ds-bootstrap.min.js script, see attached screenshots.
Scorm package format "2004 4th Edition".
It only occurs when SCORM content loaded from iframe, it works well when it loaded from browser window.
Thank you for providing those visuals! I haven't seen similar reports, so I'm glad you wrote in!
Which version of Storyline are you using? Click the Help tab, then About Storyline.
Are you comfortable with sharing the .story file? We'd love to troubleshoot it in IE11/SCORM Cloud, an industry-standard LMS testing. Simply use this private case link.
Thanks for response. We are using the latest version of Articulate 360
As I mentioned above It works well in cloud.scorm.com, they always run their modules in new browser window. But once you run scorm content in iframe - it doesn't work.
I can give you access to our test account if it helps, so you could test it both in iframe and new-window mode
I'd be curious to hear of updates, if a ticket is still submitted. We received a SCO from a contractor who is using SL360 -plus we're still stuck with SCORM 1.2. We are using SL3 ourselves, with no problems at present.
The META tag that Alex mentions is already present in the index_lms.html file but we're still seeing this error.
It looks like that was the solution for Alex, so it sounds like you may be experiencing a slightly different issue.
With your permission, I'd like you to share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.
Actually, i had a nice resolution afterwards ... after some more testing and a momentary flash-back to an earlier problem with our LMS that was similar to this one! I think everything is working well now. (until our LMS itself breaks because of what we had to do. haha)
Our LMS is rather archaic in its own HTML and was sending a different x-ua-compatible directive in the parent window/frames that it generates (to emulate an older document mode). I believe it's a quirky IE11 thing, in that this document mode trumps any x-ua-compatible directives that are included lower down in the child windows? We had a fight to get our LMS to properly render the HTML5 version of our SL courses for this same reason, until we were able to track down this hidden & offending META tag. :)
Thought i'd share this additional detail in case anyone else finds themselves on the thread with a similar situation.
8 Replies
Hi Alex,
Thank you for providing those visuals! I haven't seen similar reports, so I'm glad you wrote in!
Hi Katie,
Thanks for response. We are using the latest version of Articulate 360
As I mentioned above It works well in cloud.scorm.com, they always run their modules in new browser window. But once you run scorm content in iframe - it doesn't work.
I can give you access to our test account if it helps, so you could test it both in iframe and new-window mode
Hello Alex and welcome to E-Learning Heroes 😊
Thanks for sharing what you are seeing and for your willingness to share some additional information for testing.
I've opened a support case on your behalf so that you can work with one of our support engineers directly.
Adding <meta http-equiv="x-ua-compatible" content="IE=edge" /> header to LMS page solved the issue.
Thanks for help.
Hi Alex,
I appreciate you circling back with the code fix and working with us! You know where to find us if you need anything else. 😀
Hi Everyone,
I'd be curious to hear of updates, if a ticket is still submitted. We received a SCO from a contractor who is using SL360 -plus we're still stuck with SCORM 1.2. We are using SL3 ourselves, with no problems at present.
The META tag that Alex mentions is already present in the index_lms.html file but we're still seeing this error.
Thanx. Terry
Hi Terry,
It looks like that was the solution for Alex, so it sounds like you may be experiencing a slightly different issue.
With your permission, I'd like you to share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.
Hey Leslie,
Actually, i had a nice resolution afterwards ... after some more testing and a momentary flash-back to an earlier problem with our LMS that was similar to this one! I think everything is working well now. (until our LMS itself breaks because of what we had to do. haha)
Our LMS is rather archaic in its own HTML and was sending a different x-ua-compatible directive in the parent window/frames that it generates (to emulate an older document mode). I believe it's a quirky IE11 thing, in that this document mode trumps any x-ua-compatible directives that are included lower down in the child windows? We had a fight to get our LMS to properly render the HTML5 version of our SL courses for this same reason, until we were able to track down this hidden & offending META tag. :)
Thought i'd share this additional detail in case anyone else finds themselves on the thread with a similar situation.
Thanx Leslie.