Hello there, Thanks for bringing this to our attention!
We want to assure you that this issue has been escalated internally and our product team is already aware of it. While we cannot make any promises, please know that we are actively considering it. We use votes to gauge interest from the community and prioritize. Feel free to Vote up!
We also appreciate those of you who have already shared workarounds! If you have any more creative solutions for specific cases, we encourage you to share them. Your input is greatly valued.
Thanks,
Figma Workaround.
I have never heard this term associated with any other program as often as Figma.
Figma should produce their own “workaround encyclopedia”
Maybe title it “We are sorry to have wasted your time” but this is how you fix what doesnt work as it supposed to.
that worked, thank you!
I understand product deveoplment is huge especially now with AI
I really think FIGMA needs to test and fix what it has currently.
_ these little “workarounds” are needed far to often.
your workaround can work with a bottom navigation bar. Nonetheless, not with
sticky menus and fixed headers are not possible…
the collective waste of time for all users is measured in decades.
why hasnt Figma fixed this yet???
Annoying in deed… As I had to create a custom clickable backdrop as a Workaround… now I need a workaround to make my workaround working… arfff…
How do we vote for this issue? Just commenting that it’s still happening?
2024 and still happening. Had this issue while doing some usability tests and had to dismiss lots of findings, client feedbacks and reschedule the whole thing 😦
Let’s wait until 2030 and they’re gonna lock it behind paywall lol
Voted to hopefully bump this up even after a three year wait… I’m shocked that this is acceptable and expected behavior.
Figma is a prototyping tool and NOTHING behaves this way in web or app interface. If an element is behind another one, it cannot be clicked. This runs the risk of ruining so many usability tests.
Please fix this critical issue, Figma.
Also having this issue, it’s super annoying. I can’t use the fixes as have a transparency effect applied so I need to be able to see the background underneath my fixed layer.
I can’t believe that this is not something that has been solved by Figma. I think I had topic about this posted a year or so ago.
This worked for me! Thank you so much for sharing this solution.
Still happening which is very annoying, especially when using the mouse enter trick since there is no “enter screen” trigger,
now I have a sticky frame that triggers itself because of scrolled content below it
also, a scroll control within a frame and not just the page would solve it but let’s leave all the basic functions aside and focus on the AI magic word which currently doesn’t help anyone to actually do the basic work wich is not currently available
It seems the problem is gonna to still at 2025, right? It’s hard to keep positive when I see it has been posted 3 years ago and Figma don’t take any action.
Still after all these years it did not get a patch.
I added a condition on click and when that position absolute is on top users are able to interact with buttons right behind it.
Please fix this.
I can’t believe that this is still happening. It is SUCH a basic understanding that clickable elements on a lower layer (or z-index) SHOULD NOT BE CLICKABLE! Figma…shame on you for not addressing basic issues like this after years of customers bringing it up.
Just ran a UXR session that was totally derailed by a clickable element opening up because it happened to be right underneath another clickable element in my overlay. Our participant was confused and we had to pull back the curtain to explain that the software we’re using (Figma, and they know it) is problematic.
