Skip to main content
xxver
xxver
New Member
October 9, 2025
Solved

Why can I click on a button under an absolute element in a prototype?

If I have an element under an absolute in the layout, I can click on the element under that absolute, which is very annoying. I have multiple simultaneous clicks in my prototype.

This topic has been closed for replies.
djv
djvSolution
Community Support
October 10, 2025

Thanks for the additional context, ​@xxver! 

This is actually expected behavior. This was a design decision made by our Prototyping team to ensure that frames without interactions do not block interactions. All existing prototypes with interactions rely on this behavior to function, so while I hear you, implementing what you may consider a “fix” will likely cause other major prototyping bugs.

This is on our team’s radar as a feature request to reconsider how interactions currently work and make future improvements though. We don’t have an exact timeline to share on when or if this will be changed:

 

View in thread

3 replies

djv
Figmate
djv
Community Support
October 9, 2025

Hey ​@xxver, thanks for reaching out! 

Just to understand fully, is this specifically happening when presenting the prototype in presentation mode? Also, does your desired behavior work when absolute position is not set on that same frame?

Once I have a full understanding of what you’re expecting and hoping to achieve, I can get buy in and advice from our Auto layout team. 

xxver
xxverAuthor
New Member
October 10, 2025

Try to recreate the same structure and open the prototype in figma, and you will see that you can click on the button through the absolute. Yes, that's right, this problem is in the prototype. And it can't be outside the prototype, you can't click on the button :)

djv
Figmate
djvSolution
Community Support
October 10, 2025

Thanks for the additional context, ​@xxver! 

This is actually expected behavior. This was a design decision made by our Prototyping team to ensure that frames without interactions do not block interactions. All existing prototypes with interactions rely on this behavior to function, so while I hear you, implementing what you may consider a “fix” will likely cause other major prototyping bugs.

This is on our team’s radar as a feature request to reconsider how interactions currently work and make future improvements though. We don’t have an exact timeline to share on when or if this will be changed:

 

Terms & ConditionsAccessibility statement