Report a Problem

When attempting to delete a mode of a colour variable, Figma freezes. This happens for both desktop app and web version. Edit: Can also happen when trying to add a new mode.

I have noticed that, when I’m in design mode, certain settings that normally appear in the right-hand design panel sometimes disappear. It seemed random at first, but today I realized that it’s consistently happening whenever I toggle over to the animation panel and come back to the design panel. Specifically, my corner radius and opacity settings are disappearing. The only way I’ve found to get them back is to right click and refresh the whole file tab. The attached images show a comparison of the panel before and after I change the slide’s animation settings. You can see that the “Appearance” tools have disappeared. Has anyone else encountered this? I also filed a bug report.

Is anyone having any luck with sorting variant properties in this mighty shiny new UI? I am using components with icons that I like to sort using my own logic instead of Figma’s, and no matter how hard I drag them (from the side -yes, I know, I know) they are usually sticky? What in the actual sorting fail is this?? Often times -I genuinely wonder- if anyone from Figma is actually using Figma. This is beyond me, why they did away with the (very) old sorting that was in fact working - old folks will remember the one where variants were a different list with pill-shaped items and you could click anywhere to drag them around. Key word here is around, since if their names were short enough, you could even have two on the same line, and therefore it would take even less space compared to this abomination that in the new UI is not even working anymore. To add insult to injury, Figma is successfully unable to at least link the sorting of the layers with this abomination. Because you know, you

We noticed something strange started happening in Figma with Text Styles. Fonts started too loose its weight and width variables.

I’ve set up a custom keyboard shortcut in Figma for copying as text on my Mac. It was working great, but after the latest update, it’s broken. Please fix this issue as soon as possible. It’s making my work much harder. There are two text layers with different styles I select the first text, press the key combination (control+command+C) I expect that only the text will be copied to the clipboard, without styles (copy as text) in fact, the text with styles is copied macOS 15.0.1 (24A348) Figma Desktop App version 124.5.5

The component picker has always been a bit janky. However, the picker in the new UI is now almost unusable within projects that have many components. What I’m seeing The picker I’m talking about is the one shown when I hit SHIFT+I. I have the following issues with it: Search is painfully slow, sometimes taking up to 30 seconds to load the results In-flight searches prevent continuing to type in the search terms If I don’t type all the keywords in immediately, sometimes an in-flight search while I’m typing will clear new characters typed into the search bar I’ve emphasised the biggest issue I have with the search experience. Here is a short screen recording of the issue: What I expected The search input field is completely isolated from whether or not there is a search in progress. That means I can at least make sure I have the right search terms and wait for the results. This is pretty standard behaviour for a search input.

I downloaded and installed the latest version of Figma for macOS running over the existing installation. The app didn’t launch afterwards. I followed proposed workaround on the forum - mainly clearing Figma cash via Terminal and removing and reinstalling Figma but non of these workarounds helped. This seems to be a common issue…

Some plugins are missing from the search results in Figma, even if you type its full name. For example Styles & Variables Organizer or Noisy Gradients

I’ve been always experiencing this bug since the last update of Figma. I have these input fields with new updates. And these input fields are wrapped with a parent component called Signup Form. And this Signup Form is already used in my projects. Note that the CTAs are separate from the form (wraps all the inputs). Now, if these Input fields have updates, the Signup Form’s prototype will break. This is ready ridiculous. It happens many times. Please! Please! Please! Have a look at this.

This is so weird. Restarting the app didn’t fix it.

Did anyone encountered problem with colors in Figma? Same component, same orange, same hex code in two different files = totally different colors. Both profiles set to Display P3. Why is that?

The name of nested layer groups are truncating when there’s plenty of room to display the full name. Since we can resize the right panel, there should be no reason to set a fixed width on the text.

I have a button component with a bunch of different variants. One variant is a Disabled state where I have added a color mask to make the icons look disabled. Our icons come in a variety of colors and this has been the only guaranteed way to make sure all of the colors appear the same when disabling and then returning to normal when enabling. The issue I’m running into is when we want to resize the icon within the button, the mask breaks. This is frustrating because icons in our software do occur in many sizes but for some reason I cannot use a mask in this component unless the icon is the default size. For reference on what’s occurring, here are some images. Expected behavior when our default sized icon goes from its neutral state to disabled: Buggy behavior when the icon increases in size using a nested component. The resize occurs like normal for all states except the one that requires a mask (Disabled). Instead there is no resizing AND the mask is now broken. This is how the ma

Hello, I ran into a triggering issue while copy-pasting between versions. Variables have been applied, though the value is not good and even worse it added decimals!

Hi, I’ve created a button component with two variants: a default and a pressed state. Then I put a »While pressing« interaction on the first variant. If I add a »Tap« or »Click« interaction on the button instance to open an overlay, it stops working. The pressed state doesn’t switch back. Same with »Touch up.« I know, I could do a workaround with variables. But that would be way too much overhead here. Is it just not possible to use both interactions or is it bug?

The padding of the team’s font modal is set to zero. It needs to be corrected.

While in the left panel the »plus« icon to »Add new page« is permanently visible, I assume that hiding the plus icon to add or »create component property« in the right panel must be a bug. Or is there a good reason for hiding it? If not: it’s very confusing to search for a hidden button … Left panel Right panel default Right panel → »Properties« label on hover

When you do a component search with Shift + I and you drag a component you want onto the canvas the Actions popup doesn’t disappear and it’s annoying that it stays open. The Actions popup goes away though if I click on the Insert button or press enter.

Hi there, So lets say I have a layer with a fix W and H, but I want to switch the W to be in “Hug Content” mode, once I switch it to be so, the H becomes also “Hug Content”. Why? I want the W only to be in “Hug Content” mode and the H in fixed. I would love if you could fix it. Applying mode to one of them (W/H) should not apply to the other (As I think at least). Now, I have to switch to “Hug Content”, and then re-apply to the other one “Fixed”. Thanks - and keep up with the good work, big fan 😎

In the new AI feature, I clicked a menu item (New interface, Beta) and now its switched me back to the old interface and it seems I can’t switch back.

Hey all hoping someone has a solution to a real headscratcher we stumbled across today. We’re building out a prototype for testing where we load component instances as overlays. This modal overlay has a number of auto layouts using hug width/height. These auto layouts work as expected in prototype mode when added to a page. But if we load the component as an overlay the hug height/width breaks: This is what it looks like on the page in prototype mode: And this is what the same component looks like when loaded as an overlay: As you can see many auto-layouts break but only when shown as an overlay: List item Partner description Earn & redeem Points tags Special offers heading Active competition label While detaching the component fixes the issue we obviously don’t want to do this because it completely messes with our workflow for updating components. Has anyone faced this issue before or know of a potential solution? Thanks!

Myself and many in my team are experiencing issues with Figma links not opening in the correct position or page. Has anyone else experienced this?

In dark mode, the color contrast for text on tab background doesn’t meet WCAG AA standards. I don’t personally struggle with any visual impairments but I find reading the tab bar difficult. For some reason when I switch context to a different screen, the tab bar becomes darker and the contrast is great. Is this a bug or a feature? See screenshots for context.

Hi. Not sure if it’s caused by new UI3 or it’s a bug. But this happens: Loom video I have components for icons. Just atomic 24x24 icons, all named the same way (“color”). Then I have interactive component for icon button. Simple hover with color change. There’s “swap instance” set. In a prototype I use icon buttons. One of them - search - opens an input. Close icon button “x” acts weirdly! Figma file here Any idea what to change?

I’ve been building components using variables and it’s been great. However, last week everything BROKE. Any file with a linked component that uses variables does not pull correctly. I’ve reached out to support, but wanted to create a post incase anyone finds a fix. Example of how components are pulling through: