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

A

anon86689426

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.

A

anon86689426

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???

Laurent_Gaulhiac

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…

Bevers_Cherrie_CORP

New Member

How do we vote for this issue? Just commenting that it’s still happening?

Luis_Eduardo_Carvalho_Mello

New Member

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 😦

D

D_ng_Bach_Khoa

Let’s wait until 2030 and they’re gonna lock it behind paywall lol

I

ImaPickle

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.

Lauryn_Lesley1

Please fix this critical issue, Figma.

Sophie_Price

New Member

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.