How in god’s name has this issue been open since 2021? It isn’t a feature request, it’s a bug report. This is really fundamental functionality.

You can also use a boolean variable to toggle the visibility of a tooltip on mouse enter and leave. This works fine together with a click interaction as long as the tooltip is already absolutely positioned inside the component/variant.

So at the amount we can either for examples make a component either hover or click. Why can’t we have the ability to do both I aka hover so it shows hover. Then I click and it changes to click and move

The component indeed can’t have both but the instance can have the click event in addition to the hover which is controlled by the component.

If you would like to have all within the main component you could maybe use the “mouse up” respectively “touch up” trigger as a workaround on your hover state.

Btw, there already is such a feature request you can vote on:

Maybe @Figma_Product should merge this with the other issue, then?

Spoke too soon… looks like they already did. Thanks, @Figma_Product!

For instance, if I’ve added a hover effect to all the rows in my dropdown, I also want the click action to function properly. Currently, I have to remove the hover effect first and then apply the click action, which can be annoying especially when working with components.

I think it’s because of how they’ve built this feature. Basically, the hover state replaces the default state, so I guess they’d need to be able to place a click event on the hover object from the default one… Still such a stupid problem.

Replying to keep this ancient effing thread alive… 💀

Absolutely ridiculous that a hover state change with a click action on a button component. is not possible to prototype in Figma. Not even getting into the ridiculously complicated and chaotic “state management” that Figma cooked up.

I regret moving from Axure to Figma so much that I am now considering to invest the time to switch back. True prototyping in Figma is simply impossible with the current architecture.

I agree Mark, simple things like this would take a couple of seconds in Axure … but present a world of hurt when trying to protype it in Figma … Its an amazing tool for layout and design systems keep everything nice and tidy … but the maturity level of its prototyping is just enough to go from one screen to another or present hover states. Developing good UX is overly taxing and I end up having to explain in exhaustive step by step detail what each interaction needs to do … Figma can do better … i know they can 🙂 … Take a break from the dev side … and get a team to help the prototyping side of things 🙂

I really can’t believe I still have to struggle with this after YEARS xD

S-O-S ! I’m desperate because I spend so much time on this…

coming up on 4 years!!! come on Figma, this seems pretty basic???

If you are looking for workaround that does not overlap with other layers, here is something I use for a long time → Tooltips inside trigger component, or separately? - #5 by Pavlo_Kiselov

Please do it already! While you try to make tools for developers, you absolutely forget about designers!

Figma please bffr I am absolutely losing my mind trying to figure out what feels like a table stakes prototyping feature.

It’s absolutely insane that you can’t use a hover and click interaction on the same element.

This has been such a long standing issue that so many people want.

Why is it not being added?