Any button that I build fails to show its hover state the first or second time you roll over it. This happens in Preview and an HTML5 publishes. It's fine in Flash output. Doesn't matter if I build button from a shape or text field or an image, all behave the same.
This has just started happening.
I'm using Storyline 360 which I just updated this morning 01 Feb 2018.
If I build the same thing in Storyline 2 it works fine.
further to this, it only happens if you add elements to the button states, which is the whole point of button states right? So, If I start with a regular button, the hover works fine. If I edit the states and add a text field to the Normal state or Hover state, then the hover stops working on first/second rollover attempt.
Thanks for reaching out here! This is an issue we saw appear yesterday with our latest update to Storyline 360 - luckily our team is already working on a fix! We'll let you know here as soon as that's ready. I'm sorry for any extra trouble this caused you.
Hi Nick, I've got good news for you! We've just released another update to Storyline 360, and it includes a fix for the hover states problem you ran into.
4 Replies
further to this, it only happens if you add elements to the button states, which is the whole point of button states right? So, If I start with a regular button, the hover works fine. If I edit the states and add a text field to the Normal state or Hover state, then the hover stops working on first/second rollover attempt.
Hi Nick,
Thanks for reaching out here! This is an issue we saw appear yesterday with our latest update to Storyline 360 - luckily our team is already working on a fix! We'll let you know here as soon as that's ready. I'm sorry for any extra trouble this caused you.
Thanks for letting me know
Hi Nick, I've got good news for you! We've just released another update to Storyline 360, and it includes a fix for the hover states problem you ran into.
Go ahead and follow these steps to install the update, and let us know if you see any more issues!
This discussion is closed. You can start a new discussion or contact Articulate Support.