When using buttons with hover states, I noticed that there's a slight delay before I can click the button (after hovering over it).
<The Title was renamed by moderator>
When you say slight delay, can you put a number to it so that we can have a look and let you know?
Trying to insert an animated GIF here, let's see if this works. So you can see there's a slight delay before the pointer changes and the object is clickable. This is confusing to people I send prototypes to.
The ability to click waits for the hover animation to complete. So if my hover animation duration was set to 0.6s, it would take 0.6s before I would be able to click the button. This also applies to the ability to hover over other buttons - a hover animation would have to complete before the new hover animation on the new button would begin.
Exactly, and this behavior is undesirable. Users would mouse over and click a button immediately, and find that it doesn't work. IMO that's confusing.
In Prototype mode, for the Hover trigger, have you tried setting the Action to Transition, and Animation to None? There wouldn't be a delay then.
I imagine that might indeed work, but it's not the desired effect since I do want to use hover. I just think the click hotspot should be active right away.
I hope that makes sense.
Interesting, so I can see two use cases here:
So my concern is related to #2. My users are likely to be confused when they mouse over a button and immediately click it, and get no result.
I agree that the click should be immediate on hover for prototypes for both developers and end users as full animations would/should always be available if you hover and don't click (for devs to see), but we don't want to have devs code a click after an animation. Real-world use case is a button fires its click state/animation/experience on click... not after a set hover animation time.