HTML5 buttons not working after state change - Storyline 2

Also FYI this is hapening on additional slides in the project. I just pulled these out for easier uploading.

Here's the link to the html5 output. 

http://magdadiaz.com/buttontest/story_html5.html

The continue button on second slide only work in flash.

Hi Magda

I'm seeing the same behaviour in html5 output - I'm just making a couple of tweaks to your triggers to see if that will work for you - stay tuned!

Hi Magda

I've tried different things and I can't get the Continue button on Slide 1.2 to work in html5.  The fact that other slides are not working and slide 1.1 works I think is good luck.

I tried

• importing your slides into a new file
• using custom states
• using variables
• creating a new continue button
• creating a shape overlay on top of the continue button and changing state
• using triggers to change the continue buttons state on timeline start

Sorry I couldn't be more help. As you say the flash version works fine.

Hopefully someone else can chime in to assist - otherwise I would log a support ticket and get the Articulate Support guys to check it out.

Good luck.

Hi there Magda! Thank you for sharing your file here. Like you said, I can see that the continue button works as expected in Flash but not in HTML5. Since importing the slides into a new file didn't fix this issue, it would be best to get in touch with our Support Engineers here so they can work with you one-on-one to resolve this as quickly as possible. And if you do decide to open a case, please let me know your case number so I can follow along, as well! 

Thank you!! At least I am not crazy (yet)

Just filed it. Thanks for your help.

Case # 00984271 

Perfect - thanks for sharing your case number with me. I'll follow along and share updates here as they are available!

OK, here's the update from support:

"there appears to be an underlying issue with HTML5 content when a button from Slide Layer is placed on the same spot as the button from the Base Layer."

The solution/hack is to move the base button in another location.

This is a huge problem from my standpoint since it can result if bad/messy UI design but it is a least a temporary fix. Hopefully Articulate fixes this because it seems like a really basic type of functionality.

Make sure to test your html5 output as well as the flash output. This isn't a problem in the flash output but more and more clients are moving away from Flash.

Here is the solution to the files I posted.  http://bit.ly/2iNPMof

Wow - thanks for sharing Magda that will prevent a lot of hair pulling (for other folks) - lol.  Glad they found a workaround for you but I understand the frustration of having to change your design.  Good luck with your project and Happy New Year!

Hi Magda,

Thank you for sharing the update from Vic! I hear what you're saying, as this workaround has created more design work on your end. We have shared this issue with our Quality Assurance team, and we'll be sure to let you know any further information we have to share as soon as we can!

Yeah. We need to be more creative to make sure the UI doesn't look clunky. At least there was some type of solution.

I opened in Storyline 360 and tested the HTML5 version and it seems to be working. 

Thanks Zsolt!! I guess it's time to pull the trigger on the last tax deduction of the season. Unfortunately my client only has the regular Storyline 2 at the moment. Thanks for checking. This makes me happy.