HTML5 Issue - Layer Killing Base Layer
Sep 22, 2016
I am having a major publishing error. An ongoing project that i'm working on uses a screen where our viewer must enter their first and last name before they continue onto a final exam. If they do not enter their name in either the First or Last name boxes, they are prompted with a text box that shows up on a new layer telling them that they need to enter their name. No issues with the text variables or layers. The project previews everything perfectly fine. Works as programmed.
However, as soon as I publish the project to web with HTML5. This same slide will now vanish and the pop-up layer will be the only thing onscreen. I have tried viewing the project through IE, firefox, and Chrome with the same result when viewing the HTML5. Is there something within Articulate that may be the cause. I have copied this slide into a blank project and re-publish it. Seems to work fine that way. What is in my current project could be the cause?
As this is a sensitive project for a client, I can not provide you with the project file. I will however post images of what is happening. Any help would be greatly appreciated.
5 Replies
Hi Dustin!
It's hard to tell based on those images alone. The fact that it works in a new project makes me think you should import the project into a new file to see if this eliminates the issue within your project totally.
You are welcome to share your .story file privately with our support team here if needed and an NDA can be signed as well.
Hello Leslie.
My team and I found what was causing the issue but were unable to completely solve it. A Reset Results trigger was causing the error with the HTML5 story output. Any page or object we applied a reset results trigger onto would cause our storyline to go completely blank and essentially break the project.
At this time, we are dropping any HTML5 outputs of our storyline and only using the regular story file for Web. I did try to import the project into a new file as you recommended but it continued to break our project. We were able to recreate this issue multiple times as long as we were outputting HTML5. Hopefully this info can be passed along to your development team so they may investigate it further. It may be a compatibility issue with HTML5 and I hope it can be patched down the road. Thank you again for your help.
Hi Dustin!
Does this describe your set-up:
- "reset results when timeline starts " trigger on the question slide
If so, this is something that has been reported to our QA Team. I was able to better search based on your subsequent description.
I'll add this thread for both user awareness and for update when applicable.
Yes. It is the Reset Results trigger. The issue happens regardless of the type of slide or where the trigger is applied. We had it on a button and on timeline start. Both caused the issue.
Thanks Dustin.
This discussion is closed. You can start a new discussion or contact Articulate Support.