Report a Problem

I cannot see all of the comments in Figma, It only shows fews and if I resolve any of them then it will scroll but other than that it doesnt let me scroll. Filters also doesn’t show. This bug is only affecting the older version of UI design. I Use the new UI then comments does show properly.

Menu bar show/hide function. When the Actions tab is selected, you cannot select other tools because they open underneath.

Issue: Some variable names display a space within the name. For instance, Colors/Black displays as Colors/Blac k I am running Figma Desktop App version 124.6.5 on a MacBook Pro (2019). Has anyone run across this and if so, is there a fix?

We suddenly encountered broken variable names and aren’t sure how to fix them. Any guidance would be appreciated! Here is a video for better understanding -drive.google.com

This bug has been happening for months but for the last 2 weeks it has suddenly gotten worse. Just a few examples of the way it’s breaking : Buttons that are obviously supposed to hug the text, used to hug the text, will break just like that. After double clicking on the component, it’s fixed! Text that is not centered. It doesnt happen on every component equally, it just happens randomly. However, it’s obviously still not good, as it breaks by the time we deliver it to devs. Sometimes text still appears as an old version that we changed. One again, double clicking will correct to the newer text. Sometimes an element will disappear. Also sometimes it doesnt stay fixed when I exit the Figma app. The only way I have found to permanently fix it is to break away from the component or place the component again, as if that instance was broken. I obviously dont want to do that, especially since it affects so many of my frames right now.

When importing a pdf that has a cropped/masked image, the full image is displayed and the mask is discarded.

When you create text styles, and set the line heights based on percentages, in the summary view of those text styles, it looks as if the line heights are set in px. In these examples, my text styles are set to a line height of either 94%, 100%, or 138%. But it looks as if they’re 94px, 100px, and 138px: They still function as expected…but if they had a % on the end, just like they do when they’re entered, that would eliminate the risk of misinterpretation.

Anyone else having this problem? When panning or moving the canvas, some lines of the grid layout dissapear forcing me to constantly find a “sweet spot” for all lines to be visible. This happens even when zoomed in at pixel scale.

I’m working on a design system and encountered a bug thats slowing me 10x. To begin with, when I swap a component with a variable property within a larger component/variant instance and then change the variable color in the parent component, the color doesn’t update in the overridden instances with swapped components. (Check out the video example) For example in this case, when I duplicate the [Documentation/Feature Icon] component, which has an icon swap property, and swap the icon in the duplicated instance, the color gets inherited from the parent component. But when I change the color in the parent component, the color of the swapped icons in the instances remains unchanged. Is’nt this a common practice (or at least used to), is anyone experiencing this? I just noticed, this issue is happening across all my projects, though it worked fine last week. Any ideas on how to fix it? The worst part is imagine you’re designing atomic elements and creating pages using nested component i

Is anyone else experiencing this? > text styles turning bold randomly without using cmd+b. When I create a frame around a style is also triggering my text style to become bold. It’s driving me CRAZY. I’ve been experiencing SO MANY bugs it’s hard to get work done without feeling frustrated and gaslit.

I’m not sure if this is a bug or a feature request, but I ran into an issue when helping another designer with their prototype today. Clicking on a logo in the prototype should take the user back to the home page, and it was, but then clicking on it again (from the home page) was cycling through other frames, as if clicking a previous page or back button. However, there was no interaction set on the logo (in the file). I kept digging and found that the logo component had a “on click-back” interaction at it’s source, in the library file. So while I recall seeing the “variant interactions” at times that shows interactions of nested components, I don’t know if this only goes so many layers deep or can’t show if the component is from another file or library. If it is a bug and should appear, I wanted to bring it up. If not, that would be great if it can become a feature. It would save so much time and prevent duplication and interaction conflicts on large projects and prototypes.

We have the main component library that includes all the variants of the primary component. Recently, one of my team members mentioned that the order of the component variants has changed. I attempted to identify the issue by using the CTRL + P command along with all the repair commands. It indicated that something was fixed, but despite multiple attempts to resolve it with CTRL + P, it still isn’t functioning on the other files. However, it works perfectly fine locally. I’ve attached a video for better clarity. Tried on booth Figma desktop, Google chrome browser but it’s not working. [Google Drive] Recording 2024-11-18 184727.mp4 - Google Drive

When we’re in “dark mode”, the “Return to instance” popup isn’t in the same pattern as in dark mode.

Component misalignment and need to be double-clicked

Ever since Figma decided to switch the syntax hierarchy it has become harder to showcase components. Libraries are being showcased in the wrong syntax number no matter what. Figma is running it’s latest version. We have tried several combinations, ABC characters are not an option as the library will exceed the alphabet in terms of pages. Tried combinations: Page name 1.Page name 1-Page name 1 Page name 1a, 1b Page name etc… Nothing works. Could you please take a look to this bug? PS. We refuse to use UI3 as it slows down Design workflows and it just does not work. It has the most unfortunate design (by programmers) decisions. Don’t turn into adobe. We should not find “workarounds” with our work tool. 😦

When I publish a file as a library in Figma, it seems the naming conventions are being completely ignored when digging into the assets panel to grab components. it keeps the Page as a folder, but then ignores everything else and just displays the components at the deepest level. in this case, i have a page called “Feature Item.” Inside are two sections: “Vertical” and Horizontal." inside Vertical is “Feature Item Group / 4 column”, “Feature Item Group / 3 column” and “Feature Item Group / 2 column” inside Horizontal is “Feature Item Group / 2 column”, “Feature Item Group / 1 column”. when I publish this as a library and go to the assets panel in a file to grab components, the only folder that exists is the page “Feature Item”, and components are listed only as “1 Column”, “2 Column” “2 Column” “3 Column” and 4 Column which completely ignores the entire naming structure established and removing all context from the components. The instance swap menu respects the folder structure and

Hi, i wanted to publish my first Figma plugin but it says “We detected a change to your account details, please contact support@figma.com to publish this plugin”. So i got in touch with the support team but I got this reply: Thanks for reaching out! It looks like you’re contacting us from a Starter account. Customers on this plan receive support through our Community Support Forum. Now i don’t know what to do to be honest, if someone can help me resolve this issue, that would be appreciated.

I found similar posts, but they were resolved without any needed fixes. Here’s what I’ve tried: Disabled Chrome extensions Cleared Chrome cache Did hard reboot of Figma tabs and MacBook Pro This is a new issue as of 2 days ago and has not resolved. Any component I copy>paste within the same file just copies the text and nothing else. Note: I will add that this only occurs in one file. And when I paste something in or out from another file, it appears to work.

Hi there. I’m trying to create a dropdown menu component inside a nav bar, and I found out that everything works nice until I turned it into a component. The dropdown menu suddenly not work anymore. Once I detached it, it worked normally again. Is this a bug or did I do anything wrong? Link:Figma – 2 Dec 24

Please search for existing topics before posting! Press 🔍 at the upper right to search. I created the drop-down field using mouse enter and mouse leave prototype, but there is a problem, the drop-down field does not close when the word is left, how can I fix it? It only closes after hovering over the drop-down field with the mouse once

Hey all, We are currently experiencing an issue in Figma where the dev mode component playground is incorrectly breaking images in components. Whether we add the image as a fill to a frame or insert the image directly the image is flipping and being cropped in the playground. Has anyone experienced this and does anyone know of a solution?

In a certain scenario, only parts of the exported images use the correct variable mode. Given this simple variable setup in a variable library file: And this simple component in a component library file, utilizing the variables from the variable library file: When I pull in the component from the component library file into the variable library file and set the page variable mode to “dark” the component looks like this in the file: But when exported through the REST api, it looks like this: Exporting it through the UI works as expected. This bug is seen for both svg and png. How to reproduce: Create a variable library file that supports two modes (light/dark) and publish them. In a separate file, create a component using variables from the variable library file and publish it. Import component onto page in the variable library file Set entire page to alternative mode (dark) Export image using REST api (/getImage) See result.

I’m at a complete loss here and trying to figure out why. I have a main component and two identically setup instances, yet only one of the instances scales accordingly to the way i wanted it to work but the other does not scale at all and I can’t figure out why. From what I can see the properties are identical so I’m completely confused. Is this a software bug or am I missing something? I’ve attached a video for reference. You can view and make a copy of the file here to test it yourself. Figma – 28 Nov 24 Looking forward to figuring out what the heck is going on and a solution so I can fix this issue if I run into it again. Thanks in advance, -Confused

This bug can be reproduced as follows: On a component with nested components, create a new instance swap property. Add multiple preferred values. 4 or more will demonstrate the issue more clearly. Use drag-and-drop to drag a preferred value up or down. While dragging, the UI highlights the text of any of the “in between” items. In the following screenshot, I took the first item and dropped it into the third position. This is the result: Note, this does not happen on the main component’s “edit instance swap” dialog, only when initially creating the property in the “Create component property” dialog.