Report a Problem

New eyedropper functionality enables users to get around variable scoping. I’ve got 5 variables scoped explicitly to a single use. When using the color selection dialog to search for compatible color variables, things are exposed as expected. However, using the eyedropper can circumvent my scopes. I’m able to apply a color variable that normally wouldn’t be available if I searched for it manually.

Hi, If I click Hide FIgma UI in preview mode, some of the actions of the Figma UI are still usable, even though the top bar is invsibile. For example if I hover the PHONE button in the top of my app, I get the Figma tooltip asking me if I wanna follow one of my colleagues.

Hello! We recreated our Component Library with Modes and Variables. Unfortunately when I wanna use my components in working file (Libraries are added to File) some components aren’t appearing by switching the modes. It seems to have issues with nested components and changing properties with modes when a component variant is “reloaded/lazy loaded”. Works only fine for the first mode. It’s a massive issue now since we aren’t able to work properly. First I thought it has to do with hidden component (we are using _parts oftentimes) but even after publishing the part component it doesn’t work. Are there anybody with the same issue and a solution? Seems like a bug for me Edit: I detached the breakpoint property and set it manually on “basic” now it’s showing. So I assume it has to do with the property variable Edit2: It works with the browser bar. the difference: theres no nested component

Hello Figma Team, I am reaching out to provide feedback on a recent update. Please note that this email was translated with the help of GPT, so I apologize in advance if some sentences are a bit unclear. I’ve encountered an issue with the recent changes in how the ‘variable’ property is handled for objects. The new update has made my workflow more cumbersome. Let me provide an example to explain: Let’s assume there is a text variable ‘A’, defined as ‘AA’ in ‘Mode1’ and ‘Aa’ in ‘Mode2’. In the previous version of Figma, if this variable was applied to text objects ‘C’ and ‘B’, I could easily update the variable for both objects simultaneously by selecting them together, regardless of the mode. However, in the latest update, if objects with different modes of the same variable are selected, it is no longer possible to modify the variable in bulk. This change has caused some issues in my workflow. I manage multilingual text for designed GUIs using Figma’s variable feature. To streamline t

Hi there, I have an issue with a gradient which is connected to tokens on the one hand, but on the other hand, it’s not visible in Dev Mode. It should be a white (A) to transparent (B) gradient. Gradient in the file (tokenised): A: “White Token” to B: “Transparent Token” But in Dev Mode: A: #fff to B: #fff Cheers! PS: I can’t attach screenshots.

So I’ve got a tab navigation bar which has horizontal scroll on and I have interactions where selecting a specific tab makes the bar scroll to the selected tab and change screens. However, in the prototype, if you scroll and then press a tab, the scroll position keeps moving in the direction of the previous scroll, leaving a obvious empty space, which shouldn’t be there and if try scrolling will remove it. What I want is to just have the bar scroll to the set position without leaving the empty space. If I enable “reset scroll position” the end result is what I want, but it instead of leaving empty space, it makes the tabs jump and it just looks buggy. You can view the file here: https://www.figma.com/design/mkEsPCWHQkXiYyn0DIkwWu/Horizontal-Scroll-Bug-(Copy)?node-id=0-1&node-type=canvas&t=Wzmff91dfSlOcb88-0 Hopefully the video explains it better; Preserve scroll: Reset scroll: Is there a way to have an interactive scrolling element change scroll between screens in line

When toggling visibility of frames, it seems Figma forgets to update the eye icon: In this record, you can see the “+” icon on the canvas toggling, but the eye icon doesn’t switch between the open/closed eye. As you can see, it happens with frames only - I toggled the visibility of another layer in this recording, where you can see the open/closed eye switching. It’s a small, cosmetic bug, but it’s quite confusing if the layer you’re toggling isn’t in the viewport at the moment.

Please search for existing topics before posting! Press 🔍 at the upper right to search.

Hello, I just noticed this possible UI3 bug while setting up a prototype in Figma: I was looking for which device would match the Desktop or Wireframe frame selected in the Design panel, but when I tried scrolling down to view more of the available devices, either there’s nothing after the Macintosh (???) part or this is the end of the list and it’s just not rendering properly.

When presenting a Prototype, the option Fit Width doesn’t seem to be working as expected. When presenting in a bigger display the artboard doesn’t stretch, it doesn’t fit to the width of the screen. I suppose it is to protect pixel stretching but that is far more less to happen or to be a problem then the usefulness of it working correctly. I use to work in lower resolutions to save resources (local and server wise). But then when I have to present my work it’s framed on the sides because it doesn’t stretch. Thank you

Recentemente estou percebendo alguns bugs ao decorrer do meu trabalho, bugs que não existiam antes. Componentes SVG se quebrando sem motivo. Componentes de input, ao pegar o componente filho e alterar o texto da segunda variante, quando voltamos para o default o texto alterado na segunda variante volta ao padrão do componente local pai. Isso não acontecia antes.

Hello, This issue has been already raised in here: Interactive component bug when prototyping with overlays but received no responses and was closed. However, the issue still persists, my case is exactly the same as described in the original topic, meaning: Components (i.e. Buttons) with interactive states (default, hover, press) work well when used on prototypes that have a simple on Click interaction paired with Navigate to... option; However, when the same component is used in local prototype but assigned a transition of Open Overlay or Scroll to... it does not work as expected; Can someone from @figma confirm it’s a known bug and what would be the ETA on resolving that?

Hey guys, The RETURN TO INSTANCE feature, which is so very useful, doesn’t show up any more. But thank you so much for the useless UI3, we really appreciate it.

1. Describe the bug/issue you’re running into? Option-drag a locked layer results in duplicating the locked layer. 2. Are you able to consistently reproduce it? If so what are the steps? Yes. Any locked layer. 3. Share a screenshot, recording, console log, link to the file, etc. 4. Is the issue only happening in desktop app or a specific browser , or both? Desktop app. 5. What OS/version and/or browser/version are you using? MacOS 11.2.3

I want to export frames in a file into a single PDF. The containers are frames, not groups. They export individually just fine. When I go to File> Export frames to PDF, I get an error that says “There are no top level frames on the current page to export”.

I’m trying to merge changes back from a branch and I’m being prompted to resolve conflicts first. However when I hit “Resolve conflicts”, the dialog just closes and nothing happens. If I try again, I get the same screen with the same message so I’m unable to merge anything. Is this a known issue?

How to fix this issue ? it’s literally glitching or bug

I try to use the text shortcuts for making text bold etc. but only the underline option is blue and available in the text shortcuts. Other shortcuts in other tabs are available. I am using the German keyboard layout but also changing to US qwerty or other layouts does not work. I am on windows 11 and tried it both, inside the desktop and browser app.

I don’t know if this is a bug but why is there this random dark pill at the bottom of my canvas… it doesn’t do anything when I click it. I refreshed the page (I’m using Figma in my browser) and it disappears. But sometimes it comes back.

I’ve noticed that lately when there’s a shape with constraints (e.g.; sticking at the bottom of the page), it works when you drag and expand the frame but if you hit the “Resize to fit” button it won’t stick to the bottom. This is annoying because you need to adjust manually the corresponding shape to the right position after using the “Resize to fit” option. You can check it out in the video above 👆

Hey everyone, I think Adobe has infiltrated Figma and they’re trying to sabotage it. How is this SMART ANIMATE? Rsdifndsghifsbng

Figma is starting to drive me insane, the amount of bugs is ridiculous, I usually find workarounds because I can’t wait for 6 months for something to get fixed, but I’VE HAD IT! You release some crap UI nobody likes, INSTEAD OF FIXING WHAT WE ARE ALREADY USING AND LOVING MOST OF TIHE TIME. Did Adobe infiltrate employees and they’re trying to sabotage you? Why the hell of all hells can’t I edit a color in a variant of an instance of a component, without all the other variants of that instance to change that color? I mean it works sometimes, but not always. In the same instance of the component I mean, not in different components. Sometimes it might work, sometimes it doesn’t, sometimes some of the changes might work, sometimes none of them. And God forbid I try to change the stroke in a variant, that never works, all the strokes will be updated in all variants of that instance. I feel like I’m playing cups and balls near the Eiffel tower with a bunch of gypsies. Maybe I’ll find the ball

Hey guys, When I preview screens, or even when I send screens to my clients for feedback, I usually have a row of screens and I cycle through them, in preview mode, using the left/right arrows, or the arrows in the bottom center of the preview view. However, if I have a prototype in that page (2 or more screens linked with interactions), this feature seizes to function in the screens that are just regular screens, not prototypes. Like if I have 30 screens which are not prototypes, so there are no interactions between them, after I hit PRESENT, I can simply cycle through those screens using the arrow keys. As soon as I add an interaction between 2 screens, cycling between the rest of the screen, which don’t have any interactions between them, no longer works. Is there a way to fix this? Thanks, Chris

There is a small bug in Figma’s rendering engine - it happens frequently after zooming and panning. I took a screenshot and added a zoomed region to illustrate: If you look closely, you can see what appears to be an interpolation or rounding error running vertically across the entire screen. It’s not clear to me when this happens, but it happens frequently enough that this issue shouldn’t be difficult to reproduce - pan and zoom around a document for a minute or so, look closely and you will see it. The workaround is to simply zoom again, which I suppose causes a full rerendering. Of course, then you pan again a moment later, and the issue returns - zoom to fix it, and so on. I’m on a Windows 11 PC with the latest version of Chrome - but I tested in Firefox as well, and the bug occurs there too. (FYI, I already submitted this issue via the bug reporting form in the app, but it didn’t have an option to attach a screenshot.)

I am not able to change the width after new UI modifications. For example: from 4px to 8px