Prevent interaction hotspots from triggering below fixed elements

eokic-hexis · 2021-05-18T16:51:07+00:00

Describe the problem your experiencing and how your idea helps solve this A scrollable (clickable) list of items triggers the interaction even if a fixed element overlaps it. Additionally, this bug occurs even if that overlaping element has a “Tap → None” Add as much context as possible (screenshots, Figma files, mockups, etc.) Stumbled upon this issue when I had to position an iOS keyboard on top of an interactive list of elements. Demo file and steps to reproduce: Start the prototype from https://www.figma.com/file/GpbLNhQGrYKCTFO8aZy8BK/Hotspot-bug Click the gray bottom rectangle with or without scrolling It wrongly triggers the hotspot from the “background” items

Forum|Forum|5 years ago
May 18, 2021
54 replies
6345 views

Describe the problem your experiencing and how your idea helps solve this
A scrollable (clickable) list of items triggers the interaction even if a fixed element overlaps it. Additionally, this bug occurs even if that overlaping element has a “Tap → None”
Add as much context as possible (screenshots, Figma files, mockups, etc.)
Stumbled upon this issue when I had to position an iOS keyboard on top of an interactive list of elements.

Demo file and steps to reproduce:

Start the prototype from https://www.figma.com/file/GpbLNhQGrYKCTFO8aZy8BK/Hotspot-bug
Click the gray bottom rectangle with or without scrolling
It wrongly triggers the hotspot from the “background” items

Share an idea

Pinned Reply By djv

Hey All, thank you for your continued feedback!

The team confirmed that this is not a bug; it’s currently expected behavior. This was a design decision to ensure that frames without interactions do not block interactions. All of your existing prototypes with interactions actually rely on this behavior to function, so implementing what you would consider a “fix” would likely cause other major prototyping bugs.

Rest-assured, this is still being tracked as a feature request by the prototyping team to better understand how it is affecting the overall community. They’re now considering how to implement this in the best way that doesn’t cause other bugs.

We appreciate your patience and understanding.

Show previous replies

P

Pushan_Barman

Do we have any fix for this? This issue is so annoying, I miss Adobe XD for simple things.

Michael55

How is this still a thing…

Bauke_Schildt

Active Member

This is a smart workaround, but this definitely shouldn’t have to be done just to have a fixed menu… And it doesn’t work if you want to have transparency in your menu.

Julia_Shlyapnikova

Active Member

I keep experiencing the same problem.

Edyn_McCarty

Still looking for a fix to this too. Not sure how this hasn’t been patched yet.

iGex

New Member

Same problem.

R

rkennedy

Oh my goodness, same!

Brandon28

New Member

same problem here, bump!

J

Junko3

Figmate

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,

A

anon86689426

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.

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO