Skip to main content

With the interactive components, a variant can now have a tooltip. But unfortunately hover and clickactions are still mutual exclusive.
I’m designing for a desktop application and having a tooltip per inputelement/button is crucial.

I went through the same situation, and I think it's absurd that this discussion is still ongoing after three years. I came to the same conclusions as you did to create this workaround, but I’ll describe my case as well. I needed this button to take me to another frame, which has a button that takes the user back to the original frame. I had set it up with Click > New Frame and While Pressing > Tooltip, but the tooltip blocked the click action from working.
 

Tolltip and Expand Button

 

What I did in another situation was simply place the click action inside a hover interaction. I believe the ideal solution would be to have a proper tooltip component and always add it to the elements that need hover tooltips. Like in this video, but you can also make the tooltip a component: 

Hover Variant w Click interaction

Hope this helps somehow now with UI3. Abraços!


Component Variants solution: 

 

Unfortunately this still doesn't work for , it shows error message when interact on it: “Couldn't play interaction: nested instance is swapped with its parent instance” Anyone know what's wrong?


@Figma 
For all people working on desktop-only projects.
Would you do us a favor and allow to use both hover and click?


this is still an issue 3 years later.

quick messing around with ai features no one wants and fix this stuff seriously


Hey! Just adding onto the dogpile… why can’t hover overlay AND click interactions be possible for a single element? I moved over to Figma because I thought my team would be able to do simple things like this. Come on Figma! Please fix this! Just for context, my team and I are currently using FigmaGov.


I’ve spent hours building detailed prototypes only to hit a wall because this basic functionality is not supported. It undermines my work and makes my prototypes feel almost embarrassing. Given the complaints in this thread and 0 meaningful feedback from Figma, exploring alternatives might actually be less time consuming and cheaper than relying on these “workarounds”.