Report a Problem

When I try to use the new beta feature “Swap component” using smart animation transition And fix the scroll position of that component. the animation jump down then up and doesn’t do the smart transition. I know it is still in beta but i want to shout out for feedback

I received the new update more than two weeks ago, and yesterday I renewed my subscription with Fikma. After that, my team and I were reverted back to the old version. Why did this happen? All I did was update the plan.

Hey Figma! I just wanted to share a quick update and what seems to be a bug I encountered while finding a solution to the issue I posted about here: Component Property Issue with Button Icon Visibility Using Variables. Is there something that i missed or is a bug? Ask the community Hey everyone, I’m currently working on button components and ran into something strange when using variables to control the visibility of icons. Here’s the issue: . [image] I set up a button component where the icon visibility is managed using a variable. It works as expected for the medium and large sizes. You can see in the right-side panel under the Layer section that the show/icon variable is visible and adjustable. . [image] However, when I switch the component to a smaller size li… The Problem It looks like there’s some weird caching behavior going on with icon components. When I set my button to a small or xsmall size, I noticed that the variables also change the icon size automatically. This is where

Hello, I have created a “Button” component with a hover state. It uses “mouse enter” in order to “change to” its hover variant. When I use such button in my design and add “click” prototype interaction to show an overlay, nothing happens on click: Prototype: After deleting the variant interaction from this instance, the good old “click” actually works: Prototype:

Anyone can explain why there is difference in dimensions of the exported image and actual frame in figma

Sooo idk if I’m missing something really basic here or if it’s maybe a bug? I’m trying to just change some text of a component via variable from Regular to Bold: Main component, variable is linked to style; variable setup is on the bottom of the image Instance, set to “view” - this should now be bold, right?! (And yes, the text styles are called “Regular” and “Bold” in the dropdown too:) Am I missing something or is this a bug? EDIT (before posting lol): Ok, I’ve just tried it in a new file with all new set up variables and all - it worked there. Thought it was an issue with my initial file but NOPE! It seems to be an issue with the font: Used the original file and just changed the font to Inter - now it’s working! One difference I found was that Inter supports variable font axes - Poppins (font I’m having the original issue with) doesn’t - could that be it? So variables for styles only work if the font supports variable font axes? Let me know y’all thoughts please 🙏

There seems to be a bug with the “match” function when renaming frames, if certain characters are used in the names, such as parentheses. I have a number of frames with nearly identical names, and I’m trying to rename them by matching a part of the name. At first I thought it was completely broken, because when pasting in the part of the name I wanted to replace, it didn’t match anything. Eventually I realized it works normally except after a certain character is entered - the close parenthesis - then it stops working. (There may be another reason it’s happening, but when I remove the parenthesis, then it matches again.) If I’m just doing something wrong or overlooking something, please let me know. Related feature request: it would be nice to make this window wider so you can actually see the full names of the layers in the Preview.

Hello, today the Noto Emoji font has disappeared from the fonts. I think it’s some kind of bug, because Noto Color Emoji is still on the list (even though it’s not supported by Figma) / (upd. SF Pro font dissapeared as well) Even though I have this font installed separately on my PC, it is still not visible in the Figma interface. So Figma Desktop doesn’t see any local fonts anymore (checked on two different PCs). In this image: on the left the window of installed fonts on the system (Noto is there), on the right the screen for selecting local fonts in Figma Upd. All this was fixed after rebooting the PC (before that I only rebooted Figma and reinstalled Figma Agent). Strange bug – I can understand that something in app was broken and local fonts were not visible, but why some cloud fonts disappeared?, I’ve encountered such a bug for the first time. Does anyone have any idea what it could be? Upd. 22 july 2024: The problem happened again, but with different fonts (monrope) 24 july 2024

I was trying to connect 2 shapes with the connector that I copied from FigJam and noticed that the connector only attaching on the left side of the shape end or on any objects in Figma. please let me know if im doing anything wrong or is this a bug. Please help!!!

As the recording shows, the content text can only be edited in default mode, but not in the dark mode, neither through layer nor component property. And if I change the default to dark mode, it cannot be edited in light mode.

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 cust

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.