HTML5 Storyline 360 Publish Multiple Issues

Hello, has anyone had a chance to look at this yet?

Hi Melissa,

Thanks for sharing your file so that we could take a look.

I cannot replicate any of the issues you reported. Curious if you could take a look at my published output here to test.

Also, are you using the latest update to Storyline 360 which is Update 13? Details here.

Chrome Issues Reported:

1. Font - letter F:

IE Issue:

1. 'What is a Confined Space?' not turning orange/clickable if you hit prev while audio playing before the slide completes, then navigating back to this slide for completion:

iPad Issue:

1. Cannot navigate to previous from air monitor layer:

Let me know what you find in your testing.

I just updated today to 13, but our vendor, Commlab,  also saw the same issues in Moodle on the Home slide and slide 5.6. They flat out said they thought it was an issue in the course an to check the triggers and make sure it was set-up properly. Two other testers have also seen the same issues in the SCORM Cloud link, and our LMS.

Have you republished since you updated or was this prior to? 

That may be the difference in what we're seeing or are you sharing that it wasn't replicated by all?

My version was update 12. When our vendor used the same SCORM file and tested in SCORM Cloud, they also saw the same issue. I don't think a republish to 13 will make any difference given the notes, or issues I have seen with 13.

Make sure your browser is allowing pages/sites to use their own fonts. I had a similar issue in firefox, but had the highlighted item in this image was unchecked.

I don't know the chrome settings off hand, but look for a display/language/appearance type setting.

Hi Leslie,

I tried to take a look at this but I noticed the menu was not locked. We have noticed that this does make a difference in testing.

You might also want to indicate what version of Chrome you are using that has this issue as Google seems to be making a lot of changes recently that impact HTML5 rendering.

Version 64.0.3282.167

Have you tried opening the module in a version of Chrome where no extensions are installed? One way to simulate this is to open an incognito window. I'm wondering if an extension is blocking the download of the font. 

Gotcha, sorry about that.

Take a look at this version Melissa.

What you are seeing on the missing F character is almost certainly because a font is not being downloaded (as established in this other thread). What I've noticed is that when an HTML5 Storyline course can't download a font that is needed ("Roboto" in the case of your title slide "Confined Space Entry"), it reverts to displaying the text in Times New Roman (what you see in your screenshot), but because Times New Roman doesn't include "font ligatures" (e.g. an "f" and an "i" close together), it shows the box character that means there isn't a character for that code.

What's weird though is that I've never seen Chrome block downloading web fonts, only IE. 

Hi Leslie,

I tested your course, and could not repeat our issues. DId you change something?

Thanks for letting me know Melissa. I just set your restricted navigation back up as you mentioned above.

So, the difference may be the latest update that we talked about here.

Hi Melissa,

I was having a (perhaps) similar font display issue the past few days, where I would see special characters showing up on top of, and sometimes in place of, characters that were supposed to be in the text.  And sometimes characters were left out all together. After doing some troubleshooting with my coworker, we realized that the font I was using ("Raleway") had duplicates of each font within that font family. I concluded that I must have downloaded the font via an external site prior to it being automatically being downloaded with the installation of Storyline.

Might be worth trying this, which was in instant fix for us:

• Make a list of any fonts you used within your Articulate project
• Close your Articulate project
• Go to your FONTS folder and delete any fonts you used in the project (make sure you're deleting entire font families, not just individual ones within the family)
• Uninstall Articulate
• Restart computer
• Reinstall Articulate
• Open project
• Republish project, then test it on the same browsers you were having issues in, and now the font should appear accurately. 

Let me know if that works at all. I've read through several different threads on here discussing font issues, and none of the suggested solutions worked until we tried this one.  Good luck!

I was confirming with multiple testers that this worked, which it seems to have. Thank you.

No problem Melissa.

Thanks for popping back in with an update.