Is anyone else experiencing your layers to be under other layers when in the timeline of the storyline file they are above and even the topmost layer??
I need it to work correctly in Safari and most slides do, but once in a while there's a hiccup and the layers are viewed incorrectly. I have tried deleted and replacing the layers, but it's not working.
When you say pane, and calling them.. are you referring to the side panel with the triggers? I understand the order of triggers in order for them to working properly. The project requires gating on the slides, and it's fine on the other 50 or so slides, but 2 slides have issues again, and rebuilding them like I used do is not solving the issue. It's only in Safari.
Yes, only in Safari, and the same treatment is on all slides have have buttons and hotspots. I took a screenshot and have attached it. It's the hover state on the next button. It's the top most layer in the timeline, but is behind the images.
I feel it it works correctly on all the other slides, I don't see why it's not on this one. This issue just started and I've presented this project a few weeks ago without the issue. It's annoying how touchy these programs are. I never know what I'm going to get when I output to Safari.
Our team would definitely want to take a look at one of these files in question. Obviously we'd want you to be able to use Storyline 360 to it's fullest potential, not just as your publishing engine. If you can send along a sample SL2 and SL360 upgraded file to our Support Engineers they'll be able to take a look here.
I'm not seeing that Erin opened a case with our Support team, so I don't have any updates on this issue. We'd love it if you could send a sample of your file to us by clicking here--if there's a bug, we want to know about it!
Be sure to let me know your case number so I can follow along and share updates here, as needed. 🙂
Thanks, Balkys! Your case is in the right queue, and I do see the zip file you attached. Would you also mind sending over the unpublished .story file? That way, we can open the file and have a look inside.
15 Replies
the layers in storyline show in the order that you call them not the order on the pane.
I may have the wrong end of the stick here, but if you have Layers 1,2,3 in that order in the pane.
But call them in the order 2,1,3 that is the order they will stack.
When you say pane, and calling them.. are you referring to the side panel with the triggers? I understand the order of triggers in order for them to working properly. The project requires gating on the slides, and it's fine on the other 50 or so slides, but 2 slides have issues again, and rebuilding them like I used do is not solving the issue. It's only in Safari.
I meant the layer pane, it is the trigger order that determines the order they display in.
Is it only safari that has the problem? It could be a HTML5 issue if you have everything right.
Yes, only in Safari, and the same treatment is on all slides have have buttons and hotspots. I took a screenshot and have attached it. It's the hover state on the next button. It's the top most layer in the timeline, but is behind the images.
I feel it it works correctly on all the other slides, I don't see why it's not on this one. This issue just started and I've presented this project a few weeks ago without the issue. It's annoying how touchy these programs are. I never know what I'm going to get when I output to Safari.
If it is only Safari, I would say this is HTML5 problem and may not be fixable.
It seems odd though.
Unfortunately the client needs the html5 version to work for ipad viewing, so using the flash version from 360 isn't going to cut it.
Thank you though phil!
I have seen a few layering issues in 360 may be worth opening a support case.
Sent from my iPhone
Yeah, I've had a lot of issues with 360. I do all the work in SL2 then output in 360 because of the need for the html5 and flash files... such a mess!
Hi Erin,
Our team would definitely want to take a look at one of these files in question. Obviously we'd want you to be able to use Storyline 360 to it's fullest potential, not just as your publishing engine. If you can send along a sample SL2 and SL360 upgraded file to our Support Engineers they'll be able to take a look here.
Hi Heroes;
Any updates for this issue?
I'm testing an Storyline 360 SCORM in multiple browser. It runs fine in all browsers but Safari.
In Safari, I'm experiencing the same issue described in this post.
Hi Balkys,
I'm not seeing that Erin opened a case with our Support team, so I don't have any updates on this issue. We'd love it if you could send a sample of your file to us by clicking here--if there's a bug, we want to know about it!
Be sure to let me know your case number so I can follow along and share updates here, as needed. 🙂
Thank you Alyssa.
I submit a case number and uploaded the zip packages. Appreciate any help you can provide.
Thanks, Balkys! Your case is in the right queue, and I do see the zip file you attached. Would you also mind sending over the unpublished .story file? That way, we can open the file and have a look inside.
You can attach it to your case through this form.
Thank you Alyssa. I just uploaded the .story file.
Hi Everyone!
I wanted to share that the issue where objects on top of the timeline appear behind video when viewed on desktop Safari and mobile is resolved!
The next step is to update Storyline 360 by heading to your Articulate 360 desktop app and clicking "Update" next to Storyline 360.
If the problem reappears, please let us know and we are happy to help!
This discussion is closed. You can start a new discussion or contact Articulate Support.