Skip to main content
eokic-hexis
May 18, 2021

Prevent interaction hotspots from triggering below fixed elements

  • May 18, 2021
  • 54 replies
  • 6302 views
  1. 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”

  2. 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:

  1. Start the prototype from https://www.figma.com/file/GpbLNhQGrYKCTFO8aZy8BK/Hotspot-bug
  2. Click the gray bottom rectangle with or without scrolling
  3. It wrongly triggers the hotspot from the “background” items
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. 

54 replies

Fabrice
September 2, 2021

I came across the same issue. Looks like it is a bug.
Workaround: Select your scrolling area frame and enable Clip content. Worked for me.
But obviously, the mere fact that your content layer is already under your keyboard layer should auto-clip in my opinion…

TinyLittleMaggie
New Member
November 15, 2021

I also came across the same issue while creating a navigation bar on top of a scrollable list of items!

Clipping content doesn’t seem to work for me? I managed to work around it by expanding all the navigation items to fill up the entire nav bar, so that there is no way to click on any “gaps” and accidentally reach the background items.

Definitely looks like a bug worth addressing soon!

Tony_Ritrivi_Tony_s_NASA_Googl
January 20, 2022

I am working on a web site prototype which we are allowing users to evaluate. Figma does not mimic normal browser behavior which will cause confusion during testing. Links on the page content area are still clickable even if the sub-menu overlays them. In the prototype link below, mouse-over the “Find Data” item… the links in the left menu are still clickable even though the menu is covering them.

Figma – 20 Aug 21

Is this a bug? Shouldn’t links that are below a layer NOT be clickable?

Michael_Michael
February 1, 2022

When a button or link has other layers on top of it, essentially hiding it from view, any on-click interactions assigned to it still work. It seems like Figma will bubble down the layers and trigger the interaction, even though the button is not visible.

Is there any way to prevent interactions from triggering, if the button/link is covered by another layer? Basically, the same way it works in real-world web design, where a link wont work if it has another element on top of it.

Adam_Ratcliffe
February 3, 2022

How do you have it such that interactive components are not clickable when there is something else on top/in front of them? ie in a mobile slide out menu i can still interact with components from the blurred out home page

Dave_Knight
February 23, 2022

Seeing this issue too. Workaround not fixing it for me.

Jedd
March 6, 2022

Okay, I think I figured this out, after hours of trying.

First of all, you have to make sure you have Overflow Scrolling and Clip Content turned OFF on your master frame.

Then, all of your scrollable content should be in a nested frame with Overflow Scrolling and Clip Content turned on.

Last, it seemed kind of hit or miss for me as I was making these changes, but I think closing out my project and reopening once all was said and done seemed to help. I think Figma needed a hard refresh to recognize these changes.

At least, it’s working for me now! fingers crossed

Hope that helps.

Rich_O_Brien
March 25, 2022

Seeing this issue across all my prototypes too… Unfortunately the clipping trick above didn’t work. An update on this would be awesome.

Jessica11
April 22, 2022

Yes I’m having this issue as well. It’s a pretty basic function, having a fixed nav over a list of items that are clickable. I’ve created boxes in the nav to ensure there’s no clickable space, but still. This is quite annoying.

McKinley
June 16, 2022

Still seeing this bug. Anything that is clickable that gets scrolled underneath the fixed content (the top nav) is STILL clickable through the top nav. Extremely annoying.