Studio '13 and Google Chrome

Is anyone else having trouble with Studio '13 courses and Google Chrome? Starting this summer (2017), Studio '13 courses in Google Chrome have become much more problematic. Especially having problems with courses getting to a quiz and either the participant cannot answer the quiz question or the quiz question is already selected and showing marked as wrong. Participant is generally stuck at that point since many of our clients require restricted navigation. Running courses in Microsoft Internet Explorer seems to be the only way to resolve the problems. (This can be courses launched from a webpage or LMS.)

7 Replies
Ashley Terwilliger

Hi Brian,

My initial thought is that you've run into the issue where  Chrome has started to block Flash, and that perhaps there are some issues with the HTML5 output? If it's working in IE - I assume that's still showing the Flash output.

One easy way to check is to look at the end of the web URL - does it show story.html or story_html5.html? The latter would be the HTML5 output.

Take a look at this article on a few ways to deal with Chrome blocking Flash and let us know if you'd like us to take a look at your course too! 

Daniel  Feerst

Yes. Constant problems. The software is not detecting the type of browser--and jumping to the right format. I used to give everyone presentation.html -- no problems! Now people are getting white screens, the test results not showing past typing a name in the box.. So, I am telling people to use presentation.html5 with Chrome and presentation.html with other browsers. I believe that is doing the trick, but unsophisticated people are not following instructions. I am not certain about Microsoft Edge. I embedding a PDF certificate of completion on the last pages of courses as a back up option.

Daniel  Feerst

Ashley, what does this mean: "If you're using Storyline 1, Storyline 2, or Studio '13 and you include HTML5 output when you publish, you can bypass the Flash output and launch the HTML5 course directly. Just link to the following file in your published output, depending on the app you used"

I can by past html5 but not the html.

Brian Keefer

We had a lot of problems with Microsoft Edge and Studio '13 output. We have come to the conclusion that we have to move on from Articulate Studio '13. Studio '13's HTML5 output is way too buggy. The next question for us is whether to use Studio 360, Storyline 360, or some other company's product. Initial testing shows that Studio 360's HTML5 output is not as bad but still pretty buggy as well.