Forum Discussion
Hover state on objects in a group - expected behaviour?
Yes, hover applies to the whole group, which is a handy feature of groups, but it can totally work against you like in your case here.
You could animate those objects seperately or you could leave it as is, and then show your separate objects over the menu, once the animation completes, so you have the objects nice and sepearate for the user to click. I hope this made sense. :)
This cannot be intended... Check this sample and post..
https://community.articulate.com/discussions/articulate-storyline/buggy-behaviour-of-buttons-and-checkboxes-in-a-group
The benefit of groups is only good if you can add anything and get the same behaviour as when not grouping them. If adding multiple UX elements makes them all act on hover...as now is...its a bug. If i want a group to act as a whole, i add a hotspot in it and add the trigger i want there...
As is now...groups cannot be used with multiple UX elements.