When using an interactive component in a prototype, "Click" doesn't execute

Instead of Mouse Down, use While Pressing

1 Like

Figma refuses to fix this bug … It always ruins my workflow before a big presentation

1 Like

I’m experiencing this same problem right now. Makes interactive components useless for me. Will there be a solution to this?

1 Like

Still running into issues with this ‘click’ interaction and having to resort to use ‘mouse up’ instead. Please fix this figma.

I run into this constantly, but realized why it’s happening; if you make a variant for the hover state of your interactive component, that variant is the new component present in your main scene. So linking a click from the default component won’t work. You must link from the hover variant to the new target frame.

Sorta defeats the purpose of keeping tidy components independent of the main artboards, but whatever. Still hoping Figma will fix this someday soon so you can hover and click from the same component.


Any news? I have the same problem…

1 Like

+1 I have the same problem…

Seems like no solution to this yet as I’m currently having the same problem.

Mouse up or down or while pressing doesn’t work at all. IT STILL ignores the “on click” interaction.

Seems like duplicating the text or button inside the hover component is the solution for me.

I used the sub-menu asset to apply the Mouse Enter and On click interaction to my page.

Can not still properly use interactive component triggers and prototype triggers. Any solution? @Figma_Support

On top of this, I’m having an issue where interaction targets are disappearing when clicking through component variants. Like an arrow to expand a menu; the arrow is part of a nested component that services the encompassing component, and if you change through variants in prototype mode, sometimes the button just stops recognizing inputs.

I’ve triple checked that all layer names and layer structures are identical to facilitate this component but it still keep breaking.

Same problem, now over 2 years later. Figma’s silence on this is astounding @Figma_Support

1 Like