I created several courses for a client and delivered them in January 2017. In October 2017, Chrome released a significant update to their product and I am now going back through these courses to confirm no issues have been created as a result of this update. I wanted to reach out to the E-Learning Heroes community to ask if there are any known issues with this latest Chrome release and any SL2 courses created prior to Oct 2017 so I can have some guidance if there are areas in these courses I need to focus on confirming they are still working. I've have done some online searching for information but I'm really not coming up with anything relevant.
If anyone from the staff is reading this, my problems include the state of a button not changing from normal to visited (color change only) with a trigger and the results of a quiz are showing on the results slide however they are not appearing on a slide layer. Both work fine in IE. I'm running the latest version of SL2. My course is running in an LMS. Suggestions?
Do you know if you're seeing the Flash or HTML5 output in Chrome or IE? Also, have you looked at testing it outside your LMS? For example you could use SCORM Cloud.
Well, I'm not sure how I can tell if it's Flash or HTML5 but since I don't use Flash, I'll guess it's the HTML5.
I typically test it when I publish it to the web in SL2. What does testing it in SCORM Cloud allow me to do? (Sorry I just read the link for SCORM Cloud and I'll keep that handy.) The course works fine in our LMS using IE. It has hick-ups using our LMS in Chrome.
You can check if the browser you're using has disabled Flash, but since it's working in IE + your LMS, I suspect you're seeing the Flash output (or at least I'd hope so since IE isn't a supported HTML5 browser for Storyline 2.).
Another option is to publish for Web and upload to Tempshare or a similar testing platform - that would again help you confirm how it behaves outside your LMS. There you could also see if your browser is defaulting to HTML5, as you'll find the end of the course URL changes. Flash would look like story.html and the HTML5 output would end with story_html5.html.
Also, if you're able to test at SCORM Cloud that'll be good information to share with your LMS team. Perhaps they have limited support for HTML5 output? Worth uploading there for a quick test!
Hi Ashley, I changed the Flash Setting to "always allow" vs "ask" and the triggers/states appear to work in Chrome now. I hope that was the fix! I'll try it again with another course I created. I appreciate your responses. Thanks!
6 Replies
Sue, I'm having similar problems with SL2 running in Chrome 63.
I'm surprised no one has responded to this post. There is another thread going but it's very old. https://community.articulate.com/discussions/articulate-storyline/articulate-2-courses-have-issues-in-chrome
If anyone from the staff is reading this, my problems include the state of a button not changing from normal to visited (color change only) with a trigger and the results of a quiz are showing on the results slide however they are not appearing on a slide layer. Both work fine in IE. I'm running the latest version of SL2. My course is running in an LMS. Suggestions?
Hi D,
Do you know if you're seeing the Flash or HTML5 output in Chrome or IE? Also, have you looked at testing it outside your LMS? For example you could use SCORM Cloud.
Well, I'm not sure how I can tell if it's Flash or HTML5 but since I don't use Flash, I'll guess it's the HTML5.
I typically test it when I publish it to the web in SL2. What does testing it in SCORM Cloud allow me to do? (Sorry I just read the link for SCORM Cloud and I'll keep that handy.) The course works fine in our LMS using IE. It has hick-ups using our LMS in Chrome.
Hi D,
You can check if the browser you're using has disabled Flash, but since it's working in IE + your LMS, I suspect you're seeing the Flash output (or at least I'd hope so since IE isn't a supported HTML5 browser for Storyline 2.).
Another option is to publish for Web and upload to Tempshare or a similar testing platform - that would again help you confirm how it behaves outside your LMS. There you could also see if your browser is defaulting to HTML5, as you'll find the end of the course URL changes. Flash would look like story.html and the HTML5 output would end with story_html5.html.
Also, if you're able to test at SCORM Cloud that'll be good information to share with your LMS team. Perhaps they have limited support for HTML5 output? Worth uploading there for a quick test!
Hi Ashley, I changed the Flash Setting to "always allow" vs "ask" and the triggers/states appear to work in Chrome now. I hope that was the fix! I'll try it again with another course I created. I appreciate your responses. Thanks!
Thanks for that update, D! And definitely let me know what else you need.
This discussion is closed. You can start a new discussion or contact Articulate Support.