html5 hotspot acting differently than flash version

Oct 03, 2017

Karen Siugzda
By Karen Siugzda

I'm banging my head trying to figure out why a hotspot button is working fine in flash version, but not in html5 version.

In html5 version, button activates layer, as it should. However, when layer closes, that same button should continue to activate the layer each time I come back to the base layer. It's only working once, then stops.  Works perfectly fine in flash version.

html5 version

flash version

Story file attached.

:::: update 10/4/17

I now notice that the hotspot is still on the screen, even after the layer slides away, which is leading me to believe that for SOME reason, the layer is not properly hiding itself, even though I have a trigger set to hide it (and it hides just fine in flash version.) You can see the finger icon on the hotspot below.

And my most recent test I even added a trigger on the base layer to hide the other layer when the base timeline starts (and when it restarts after layer goes away.) Still not working. ugh.

Help??

 

you can see where the hot spot is appearing, but it shouldn

 

Any insight is appreciated.

Thanks!!

3 Replies
Crystal Horn
over 6 years ago10/04/17 at 11:37 pm (UTC)

Hi Karen.  Thanks for such a great breakdown of the problem.  I saw exactly what you were talking about when testing your output links.

I made a couple of small changes to your file:

  1. I created a new custom hover state for the pull-out arrows (alt >> button).  I didn't want the built-in hover state of that object to interfere with the trigger to change to the hover state when hovering over the hotspot.  The built-in hover state has invisible triggers that will fire, and if the hotspot doesn't completely cover that object, you could get conflicting state changes on the object.
  2. I changed the trigger to hide the layer to fire when the motion path on the second group of objects completes (NOW group on motion path 2).  The trigger to hide the layer was originally built to fire when the first group completed the animation, which theoretically left no room for the second group to complete animation.  Triggers will fire in the order they're listed.

I tested using a trigger to close a layer when animation completes in HTML5 in a fresh slide, and it functioned fine.  I wasn't sure why your particular layer was not closing as expected.  But with these changes, the layer appears to be closing.  The hotspot is still present on the base layer, however, as indicated by the hand cursor.

So this modified version is working, with the exception of the sticky hotspot.  Check it out and let me know if this works well enough for you.

We have an issue documented where the hotspot remains after a layer, so I'm going to include your post in our report.  Thanks for reaching out with your file!

Karen Siugzda
over 6 years ago10/05/17 at 12:42 pm (UTC)

Thanks for your work on this, Crystal!

Looking at your sample, it is working better now. I do notice that the "leftover" hotspots on both the base layer and the slide out layer do cause a potential issue. Because the cursor is still showing the finger icon, indicating its actionable, I clicked it to see what would happen. When I click those "leftover" hotspots it sporadically breaks the slideout function. Meaning, the button opens the slide out but then at some point it stops working if I've randomly clicked those leftover hotspots.

I'm glad it's working as well as it is now, with your fixes. Thank you. :) 

I am still a bit concerned that there is potential for a user to randomly click a "leftover" hotspot. Since this is an interactive learning tool, people do look for cursor change to indicate interactivity.

Hopefully this "leftover" hotspot bug can be fixed ASAP

 

This discussion is closed. You can start a new discussion or contact Articulate Support.