Slide Layers Out of Order - Problem in Safari Has Now Spread to Chrome - Any Insights or Fixes?
Feb 18, 2019
The latest version of Chrome has broken nearly all of my Storyline 3 modules -- and it likely has broken many of yours too!
For a long time, a bug in the scaling function of Storyline 3 -- where the module is set to scale to fit the browser window -- affected only Safari. In this format, the order of layers on a slide is messed up, with layers inexplicably out of order. If a button is in front of an image, the image might cover up the button. The result is that this ruins the aesthetic of slides, covers up key elements that can make the course impossible to navigate, etc.
A new update to Chrome has exposed this Storyline 3 bug in Chrome -- so that modules (whenever they were created) will now suddenly have layers out of order. Go check your modules in Chrome and see if they are affected. I bet potentially millions of modules are affected -- any module that uses the setting to scale the player. If you have any navigation buttons on the slide, such as a continue button, get ready to see this button hidden behind a layer and your course impossible to navigate! For me, it has affected hundreds of modules, all of which have been ruined in one fell swoop. This is quite devastating.
This problem doesn't appear when the module is set to be locked at optimal size. Unfortunately, optimal size is much smaller, especially in Chrome. It is quite tiny in the default size of the Storyline 3 module. It might look fine on a tiny mobile screen, but on a larger PC monitor, it is too small. I've thus published my modules with the scaling.
I have explored this Safari issue with Storyline 3 support before, and the only answer was to stop using the scaling option and to use the locked player size. Because so few of my users used Safari, the problem wasn't a major one -- it wasn't ideal, but I could live with a few users encountering issues.
Now, all of a sudden over this weekend, this layer out-of-order problem affects all modules in the Chrome HTML5 playback. This presents a huge problem for me. I have hundreds of modules on my site and even more with clients in this LMS systems, and they are all set to scale. Most use Chrome, so now suddenly hundreds and hundreds of modules are messed up.
I'm not sure what to do. Republishing all could take months. I guess I might have to do this, because many will look unprofessional, error-ridden, and have key buttons blocked because the layers are out of order.
This is an enormous problem affecting nearly every module I've created. If I have to republish them all, I ideally would like the player to scale, but I want to be sure I choose an option that won't have such an epic fail as the current Storyline scaling function is experiencing.
I suspect that many other Storyline 3 users will start to see problems. Whatever changed in Chrome is going to affect so many of training users.
My questions are:
1) Is there any setting or other thing I can recommend for Chrome users that will make the modules play correctly without having to republish all of them? I don't want to have to publish several hundred modules and replace all of the ones on my site and with all clients. This is a task that would take months. If it could be avoided, that would save me a crazy amount of work.
2) Is there any setting in Storyline 3 that will fix the issue and let me use the Storyline player scaling option?
3) I could entirely abandon the Storyline player scaling option and go with the locked player. So far, this is the only option I can think of. If this is the only fix, I recommend that Storyline get rid of the scaling option, as it has just led me off a cliff.
4) Without the scaling, to deal with modules at a locked size, I could set the module size to be double its default size so they aren't so tiny on the larger PC and laptop screens of today. But how would the modules function on smaller screens if they can't scale down? Does anyone have any experience with this?
Any advice and insight would be greatly appreciated. I'm really struggling with how to deal with this monumental problem.