Report a Problem

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 insta

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 the

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.

Hi everyone, I’ve added a new property (variant) to my component. It appears in the right-hand bar after I’ve published it on my project, but it doesn’t work when I use it. I don’t get any errors when I look in the library where I created it, so I don’t understand… it seems to be a bug

I’m developing a plugin and it has been running without any issues. It suddenly stopped working and when I tried to import the manifest again, I’m getting an error: Uncaught (in promise) Error: Error invoking remote method 'web:createMultipleNewLocalFileExtensions': TypeError: Cannot read properties of undefined (reading 'path') at IpcRenderer.invoke (VM4 sandbox_bundle:2:118120) at async Object.createMultipleNewLocalFileExtensions (<anonymous>:12:11851) I then tried to create a new plugin (Figma design + FigJam) and am getting an error: Error: Error invoking remote method 'web:writeNewExtensionDirectoryToDisk': TypeError: Cannot read properties of undefined (reading 'path') at IpcRenderer.invoke (VM4 sandbox_bundle:2:118120) at async Object.writeNewExtensionDirectoryToDisk (<anonymous>:12:12906) Any ideas? Has there recently been an update in the Figma plugin API?

Hi. We heard you. We see the giant purple banner and lengthy post pinned at the top of the forum. Now give us the ability to dismiss it permanently so we do not have to scroll past it every time we want to use the forum. If Figma is good at one thing, that is annoying its users and not thinking about UX when they do things!

Greetings! I’d like to report a bug I’ve been noticing for a long time now in Figma’s prototypes. When viewing prototypes, components’ hover-interations would get stuck. Once components transition to a hover state, they wouldn’t transition back on mouse leave (when I move the cursor away). So every component that has a hover freezes in it’s hover state once I move the cursor in. The issue usually gets resolved when I reload the prototype tab, but it comes back from time to time, I’ve had this bug multiple times today already. I’m working with pretty large artboards that have a fair number of components and a lot of them have hovers, so reloading a tab takes some time. I’ve noticed this issue in multiple files, different projects, etc — it just kinda happens sometimes. I’m assuming it mostly affects larger files. Figured I’d post about it here, there might be someone else experiencing the same issue. If possible, perhaps there’s a chance someone could look into it. Thanks 🙂 Best regard

Hey, can somebody help me, I cant choose where to show the gif anymore as a thumbnail… is there somebody who would know why? Screenshot 2024-10-25 at 13.05.15|690x445

I’ve noticed that position of an absolutely elements within a frame get messed up after you delete the frame and undo. They are no longer in the original coordinate after undo. It doesn’t always happen, but it seems to happen when you delete a large number of frames (via cmd+a, delete, and cmd+z). Attached is the impacted screen. instead of the sticky / floating nav bar remaining bottom aligned to its autolayout container, it gets pushed even further down and gets clipped. Sometimes it gets pushed ‘up’ as well. This issue has existed for a few years. As long as I remember.

Here is an example of what it does : If I move the Avatar group one time no problem; If I move it another time, the group is flattened : all groups or variable inside are in the level 0 of the tree. If only a tool could sort variables alphabetically 🙂

When I add description to component set, the description display normally. But if I add description to single component, description not show up as I expected I check the old version, it display normally, so I think it’s a bug?