Hello! Anybody know why new courses will play in Chrome, but not IE? Older courses work fine in IE, but anything I have published recently gives me the "spinning wheel of death" forever. Has anyone come across this or know what the issue could be?
I see where you reached out to the support team and that Rowie is helping you out. Thanks for sharing your latest update and your files with him there.
What was the result here? I'm having the same issue. Any idea why the course played in Flash only and not HTML 5? This defies everything I understand to be true.
HTML should work, because in theory it takes any issues with Flash out of the equation.
I'd love to know the answer to this. In the mean time, I'm going to have the vendor publish in Flash only and see in it works.
This is a very helpful, but mind-numbing topic for us e-learning folks. Any replies are welcome.
We came to the conclusion that the issue was linked to the update to Articulate 360 several months back is where the issue started. The resolution that worked for us was changing the default publishing format (under properties in the publishing window) from "HTML5 / Flash" to "Flash / HTML5" which basically means HTML5 with Flash fallback. It worked with both IE and Chrome at that point. Try publishing in that format to see if it works for you.
7 Replies
Update: If I publish as flash only, it ended up playing! But, why won't publishing as html5 work?
Hey Kara,
I see where you reached out to the support team and that Rowie is helping you out. Thanks for sharing your latest update and your files with him there.
Yes! Thank you!
What was the result here? I'm having the same issue. Any idea why the course played in Flash only and not HTML 5? This defies everything I understand to be true.
HTML should work, because in theory it takes any issues with Flash out of the equation.
I'd love to know the answer to this. In the mean time, I'm going to have the vendor publish in Flash only and see in it works.
This is a very helpful, but mind-numbing topic for us e-learning folks. Any replies are welcome.
Also, another question, does your file still play in Chrome as well?
We came to the conclusion that the issue was linked to the update to Articulate 360 several months back is where the issue started. The resolution that worked for us was changing the default publishing format (under properties in the publishing window) from "HTML5 / Flash" to "Flash / HTML5" which basically means HTML5 with Flash fallback. It worked with both IE and Chrome at that point. Try publishing in that format to see if it works for you.
Hi Justin,
If you need us to take a look at your Articulate Package, we'd be happy to do so.
You can also work privately with our support team here if needed.
This discussion is closed. You can start a new discussion or contact Articulate Support.