Hover State for buttons

Need some help here.

Context - There are 13 buttons on a page, which needs to be clicked sequentially. So i have 4 states for all the buttons i.e. Normal, Hover, Visited and Disabled. And all the buttons except the very first are set to Disabled state as there Initial state. 

Issue am facing - Now am hovering on the very first button which is active. When my cursor is moving from any path and not coming across any other button than its working fine and showing the hover effect. But if the cursor is coming from any other button(i.e. disabled) than the hover effect is not getting played. 

Hope am clear but still if not, here is another possible explanation-

BTN01 and BTN02

BTN01 is active and BTN02 is disabled(initial state)

Mouse is hovering on BTN01 from any path where its not hovering on BTN02 than the hover state of BTN01 is working fine. (i.e. pointA to BTN01 direct)

But when the mouse is moving from pointA to BTN02 to BTN01 then the hover state of BTN01 is not appearing.

 

Please help resolving if anyone faced same issue.  

 

5 Replies
Ren Gomez
Hi Shailesh,
 
Thanks for reaching out. I'm sorry that you ran into a bug we have reported where:
 
A hover state in an object does not work if you mouse over on another object with a disabled initial state.
 
We'll continue to keep an eye on it to evaluate how many customers are impacted and what impact it has on courses.
 
Here's some more detail about how we tackle bugs. I'm really sorry that I can't say when this issue will be fixed, but you're in the right place to stay updated on this bug's progress. 
Diarmaid Collins

Hi Ren. Can I ask if there are other known issues with regards the HOVER and SELECTED states of buttons?

In the past, the HOVER state would always remain, even after the button has been clicked (SELECTED) until the cursor moved away from the button (HOVER OFF) and there was a workaround provided by Matt Bibby whereby if one selected the entire contents of the SELECTED state and then copied, deleted and pasted it back in, this would now override the HOVER state and the user would be able to immediately see the SELECTED state upon clicking.

However, recently, this workaround doesn't work anymore, and the HOVER state still 'trumps' the SELECTED state, even on radio buttons. Which is a complete pain in the bum, being honest. Even if Storyline fails to behave as it should, please allow the workarounds to continue working, or at least have the grace and dignity to fix the issue in the first place.

It is so... weird... to see and hear a company rep state something like "We'll continue to keep an eye on it to evaluate how many customers are impacted and what impact it has on courses" as if that is any kind of valid response.

Even if one customer has brought up an issue it is still an issue and will remain a priority issue for that single customer until the issue is resolved.

Anyti8me Storyline fails to behave like it should, in any UX capacity (such as immediate 'feedback' on button selection) has a massive impact on any eLearning course because the user will never be sure if their response is recorded correctly, and might double or triple click, to compensate.

You know this. You guys all know this. This HOVER issue has been around for years and is still not fixed.

Lauren Connelly

Hello Diarmaid!

We are happy to clarify! We don’t have any bugs logged for issues with the hover and selected state behavior that you’ve mentioned.

The Hover state is a visual indicator that the object is still active, which it technically is unless it’s hidden or disabled. Currently, when an object is hovered, then selected, it will remain in a Hovered/Selected state until you hover off.  Here's what this behavior looks like in action:

It sounds like you’re looking for the Selected state to override the Hover state when an object is set to Selected. Since this isn’t the default behavior, I can see how this would work using custom states and triggers.

Here are two suggestions:

  • Use the disabled state, so the hover state isn’t active.
  • Add custom states and use triggers to determine when the state changes.

We update our bug reports and feature requests so that our roadmap reflects our customer needs. Prioritizing what bugs and features will make it on our roadmap is not a simple task, and we know it can feel personal. That is never our intention. I apologize if it came across as though we aren’t listening. We need your input and value anyone who takes the time to share everything from reporting a bug, suggesting a feature, and sharing where we can improve to provide customers with a stellar experience.

Lauren Connelly

Hi all!

I'm excited to return to this discussion with exciting news! We just released Storyline 360 (Build 3.55.25954.0), which includes the fix for the bug where sometimes a hover state wouldn't appear when there were disabled objects on the same slide, and sometimes text shifted when hovering over an object in a course using the classic player.

To take advantage of the newest release, make sure to update Storyline 360 in your Articulate 360 desktop app!

Please don't hesitate to reach out to us if you run into any issues updating or have additional questions. You can reach us in this discussion or by submitting a support case!

Stay well!