Report a Problem

I have a Design file that uses Slices to export component variants in different states (like on/off, light mode/dark mode). Previously, leaving the export option “Ignore overlapping layers” in the default “on” state resulted in exports that look like the Export Preview—in this case, an orange icon on a transparent field. However after a recent change, my exports now show the background fill of the component in which the slice and variant are located, contrary to the Export Preview and experience with previous versions of Figma. This behavior is consistent with the Export Preview I see when I turn “Ignore overlapping layers” off. At minimum, it seems like a bug that the Export Preview does not match the Export.

I created a couple variable collections in my Figma file. Ended up renaming one, then exported a collection, moved a group of variables to a different collection in the same Figma file, and then re-imported it to my Figma file through a Figma plugin. A few hours later I noticed many of my variables are broken, and both sets of the old-named and renamed collection both exist in the Appearance panel collection drop down (3 instead of 2). Any help on getting rid of that old collection?

Earlier this week I made a prototype that relied on variables. I have a few variables that I set to true/false which affect the visibility of components in the prototype. This all worked fine until today where now these variables seem broken. They don’t appear to update or at least the visibility doesn’t appear to update. If I close and refresh Figma occasionally SOME of them work, but I can’t get the entire prototype to function properly like it did. Can anyone help? I need to hand this off to people tomorrow to present during a tradeshow. I don’t really have the time to make individual frames for everything instead of using the variables for visibility.

When defining Scroll to interactions in a component and then using it’s instance in a prototype they don’t work. They seem to be linked to the position of the children inside the component? This feels like a bug? I have a prototype where I need to use an instance of a component with multiple variants so it can adapt to state in variables. But this now means I can’t prototype scroll to interactions. Example file:Figma – 2 Oct 24

I’ve looked everywhere and can’t seem to find a solution. I’ve recently updated my plan from student to pro and lost my UI3. I’ve contacted support and am waiting, but just wanted to see if anyone else has “lost” UI3 and if there’s anything else I can do from my end?

Autolayout stops working if you make a component out of it. A component consists of two other components. Clicking on the internal option should reveal the partition details. This works if these two components are combined by auto layout, and the main container changes its height as needed. But if they are combined into one component with auto layout, then the height of the container does not work correctly when clicked. Link to the file and video of the error I add Figma - https://www.figma.com/design/dGSxWR5NvlCE6FXsoIku6T/Auto-layout-bag?node-id=0-1&t=kIiVUF5wjfOHtfph-1 Video - Monosnap Give me a hint if there’s something wrong with the way it’s done. Thank you.

In the previous version of Figma UI 2, we were able to use a shortcut to select a frame or section and press SHIFT + 2 to zoom in on any screen or section. This feature was also accessible by double-clicking a frame or section icon from the layer panel. However, in UI 3, it is not functioning correctly. Please address this issue. Google Drive link of Video - Recording 2024-09-26 132540.mp4 - Google Drive

Lost file control in Figma- No Sidebar, Toolbar is visible. When i was working on that file suddenly the file loaded automatically i lost control of the file. There is no comment, no click option is visible. From the dashboard I again draft/copied the file but still no sidebar, toolbar, or click option was visible. Then I checked my other Figma project, and all those are ok. Please help me to solve this.

On Slide, I added a prototype link, it showa the preview with the correct prototype. But when I go in presentation mode, it loads a different prototype.

I’m having an issue with external links in Figma Slides. In a slide I have an autolayout frame with many text buttons that should redirect to different links. Links are correct on the editor (every button has their link pasted in it), but when I go to the presentation mode and test I see that all the buttons lead to the same link, which is the first one of the set.

I’m trying to make this simpler for developers to read in Dev Mode by using code syntax. When I write a custom web code syntax within a group, Dev Mode only displays my custom name without the value. I would like it to replace “group/variable-name/” with my custom name while retaining the value in each mode. What I expect to see is max-width: var(--max-w, 1328px); instead of max-width: max-w;. It works perfectly when I use Figma’s default name, but I don’t want developers to see my organization of variables in Dev Mode, as it’s irrelevant to both them and me. The only workaround is to avoid using groups in variables and rely on memory to remember what belongs to what or to create a new page for each group. Honestly, I don’t even want to see var(--max-w, but I understand I’m referencing another variable. Even so, I want to edit how that is displayed, as this information of how I’m referencing variables in Figma is unnecessary to our developers. Another issue is that when I assign a cu

When I make library updates, I not longer get the toast notifying me there are updates in files using the library. I have to discover them one by one and update each instance manually. Not sure why this changed, but it’s very time consuming and dangerous when I can’t rely on prototypes, etc. having the latest updates to components. UPDATE: now it seems to not be pushing updates at all. I’ve already tried repairing all component connections via the Quick Actions

I have to “precisely” position my cursor to grab the right scrollbar to scroll the canvas. I’m used to grabbing the browser scrollbar this way, and it would be useful in Figma as well.

There is a problem since the dev mode is out of free mode for permitting developers on Figma. When I give the dev mode permission to them they can also edit the project; I don’t want this. Developers can easily mess up design. On the other hand, we have all kinds of access on the Figma team management page like team permission, design seat and FigJam seat. Related attached photo: If Figma adds a new permission like dev mode seat it’s a better way to manage developers instead of giving each of them both edit access and dev mode access. Also, in the project sharing popup, “can access to dev mode” needs to be added. Related attached photo:

How can I keep the same image when changing variants? I have a responsive gallery component that reset images (back to the original component image) when choosing a different variant.

When I have the local variables panel open and I try to copy the value of one of them and paste it into a text that is part of the design, the combination of Ctrl+C and Ctrl+V does not work. However, it does copy the content, because I can paste it into another application, but Figma.

Different border radius value wont work. It will work if and only if it has the same value.

Hey guys, A new bug has just popped up, basically, after a few minutes of using Figma, when I try to change a variant, the dropdown appears in two places, one in the right place, and one somewhere in the left sidebar. What’s annoying is that the correct one is not functional, the one 20 miles away in the sidebar is 🙂 Just a crazy thought, why not fix bugs instead of releasing new UIs nobody likes? Thanks, Chris

I have several components in my library that share the same problem. When I change properties on an instance of the component, sometimes it resetts the text. Then I undo, and change the same property again, and now the text isn’t resetted anymore. Since it only occurs randomly, and after undoing it works properly, it looks like a bug to me. But maybe someone elese had the same problem?

Exiting the group from the file doesn’t work, it still exists. Is there any way to clear/share the record of the file?

This week I had many problems with the auto-layout. The hug auto-layout with padding in components seems to have an unstable behavior. On my recording you can see the problem, I enter 16px of padding top+bottom, and it disappears on bottom when I change the text in my instance. FYI the font I use is a Google Font, that is not supposed to bug. Please solve this problem, it is extremely restrictive 😭 I went back to the old UI because I thought that the problem came from there, but it’s not. Sorry for my English, I’m French

我有2 个 Figma 账号，现在我发现这两个账号主页左侧的项目展示上完全不一样，如何恢复到旧版样式？

Hi, I created a dropdown component. When the first option is selected and then I try to change it to another option, the first option gets chosen again. Can someone help me?

Now i always have to clear cash and restart the app, and configure each setting anew each time, I thought the problem was in the computer, that there was perhaps some kind of failure, but now it is systematic, I correlate this with the update that you somehow made this summer, during your presentation, now I understand that while your engineers were working on new functions, in particular with the autonomous layout, they made some kind of mistake, because of which everything that I have in the layout is now added for x is “fixed” and y is “hug”, all the time i made layers autolayouted… Can you please fix it? I always have to clear cash and restart the app reconfiguring everything from scratch every time it is tiring… Working with autolayout is already very difficult, it would be nice if instead of automation you would focus on eliminating errors that your new solutions cause due to the still existing old ones I’m sure I’m not the only one with a problem with the app. Since I contacted

Im not sure if this is how it’s meant to work but having a complex component with other components with it have been used to hide some of it. Though in dev mode all components are visible in the side panel although hidden in the display. We teach our devs to explore the side panel to check component structures and this adds a little caveat in the discussion. So should the side panel visuals be the same as design mode and grey out a component section while its hidden, or reveal it like in dev mode?