Skip to main content
eokic-hexis
May 18, 2021

Prevent interaction hotspots from triggering below fixed elements

  • May 18, 2021
  • 54 replies
  • 6345 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

Nicolas_Caputo
August 6, 2024

This worked for me! Thank you so much for sharing this solution.

Ziv_Feldman1
New Member
August 20, 2024

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

Yuanrui_Li
New Participant
November 10, 2024

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.

Peter000
December 10, 2024

Bump
Pls fix.
Thank you

Danial_Nazemi
New Member
December 12, 2024

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.

Nik13
December 18, 2024

bump. still a problem

Almo07
New Member
December 18, 2024

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.

Stefan_Grindley
New Member
January 28, 2025

Still a problem… 

Jono Lee
New Member
February 4, 2025

This is still happening. Please fix!!!!

Jayde Ly
New Member
April 1, 2025

Still happening, please fix. Having to clip my content frame makes it very difficult to manage the designs. I’m very disappointed that this hasn’t been fixed.