Report a Problem

Ok… here’s a strange one. After the last update (Current desktop Figma version 124.1.16) the color palette sticks to my mouse pointer when selecting a color from the library. It’s really annoying, see the video. I’m not holding my mouse buttons or whatever, it happens after the selection/click. When I’m clicking more at the bottom of the palette not in the middle. This bug happens when I did not scroll through my color palette It happens on my Apple MacBook M3 Pro Sonoma 14.1 and HP ProBook Windows 10 Enterprise. If this bug could be removed I would be a very happy fellow 😀 This bug really holding me back from doing my work properly.

With the latest release prototypes now have an option to set scaling “Responsive”. This is mega, but seems that overlays (elements/frames triggered via interactions) do not behave as responsive, yet? Like overlays are not aware they sit inside responsive viewport and they should adapt accordingly. Any hacks to overcome this?

I tried to share prototypes and a slide presentation with a client yesterday, and neither loaded for them in Chrome. It was stuck on the Figma loading bar. I was able to replicate the issue on my end as well. Brave works fine. Here are the versions client and then myself are on: Version 127.0.6533.100 (Official Build) (64-bit) Version 127.0.6533.120 (Official Build) (x86_64)

I would expect that this should be covered as a fix soon I have had to pick super short names for my variables to work around this but when using collections it becomes impossible. I find myself often disconnecting a component from variable only to ensure it’s linked to the correct one, which far from efficient.

For past 2 or 3 days, I’m expecting a weird bug inside Figma. I am unable to delete layers life, frame, shape or image, when they are inside any other frame. i happens when we update layer’s lock/unlock or visibility properties.

Once again this week I’ve ran into an issue concerning components/instances and variables. I was using a simple solid color gradient to mock a scroll fade, and when changing the color or layout of the gradient, all instances would update correctly as expected. But now since binding a local variable to the gradient (a local style) so that the fade gradient dynamically switches between light and dark variable modes, the instances do not update automatically, requiring me to find and click reset all changes on every instance. Moreover, even if an instance has been ‘reset’, if nested in another instance, the wrong variable mode is displayed. Only reason I started paying this last month for Figma was to refactor my files to be more dynamic with variables, yet it’s just constant headaches so far and my work has come to a halt. I’ve ran into more bugs in the last 2 weeks than I have with 3 years of daily use.

1. Describe the bug/issue you’re running into? FigJam allows the user to select items, right click and ‘copy as PNG’ When this is pasted in to another program or document on DESKTOP, the transparency areas are not honoured and turn black. Suggest that FigJam should output a PDF. 2. Are you able to consistently reproduce it? If so what are the steps? Select items, right click, copy as PNG Open desktop program (e.g. Outlook, Word, Illustrator, Photoshop, InDesign) Paste PNG 3. Share a screenshot, recording, console log, link to the file, etc. 4. Is the issue only happening in desktop app or a specific browser , or both? Happens when copying PNG from FigJam to desktop program. 5. What OS/version and/or browser/version are you using?

I’m back asking about something I don’t understand regarding shared libraries and the logic of the colour picker. Consider this use case: I have a Ui library shared called 💎 UI Token This library has 2 variable collections for colours Core Tokens → All Raw colours (not accessible outside of the library file) 🎨 UI Core → for UI elements, surface, border, icons, text… 🎨 UI Extended → Brand, hints and other non common use case Now I’ve named those collection in such way that when I choose a colour to assign in the picker, the 🎨 UI Core shows first in the list and 🎨 UI Extended second. Like in the screenshot of the Local Colour picker (within 💎 UI Token) For some reason when you open the same picker in another file the sorting order of the libraries is not the same anymore… 🎨 UI Extended is now first and 🎨 UI Core is second. I thought maybe sorting is reversed by mistake in shared library colour pickers. So I renamed th

1. Describe the bug/issue you’re running into? When I copy and paste a flow from FigJam into Figma, there is unexpected behavior whether flows show up or stay connected inside of Frames and Components. It seems the main issue is that connectors don’t stay connected inside of components, and FigJam flow elements don’t want to be placed inside of components. It also seems like Figma doesn’t know what to do with connectors that are not linked to a node on a Frame. My example shows many frames that have multiple connectors because of multiple touchpoints and paths on each screen. 2. Are you able to consistently reproduce it? If so what are the steps? Yes. Trying to bring flow into Figma Frame Copy flow from FigJam Paste into Figma on canvas. Try to drag into frame. SUCCESS! Either select all elements and create a Frame from selection, or select destination frame and then paste into selection. SUCCESS! Trying to bring flows into a Figma Component Copy flow from FigJam Paste into Figma on

Hi, we notice an issue inspecting icons in Dev mode. When we select an icon that contains a colour token, we can’t select the shape in dev Mode, and them we can’t see the token colour. Is there any way to see it? Thank you

Hi everyone The “select matching layers” not working after enabling new UI (recent Update) and then going back. Do any of you facing such an issue?

I’m using heavily variables in my prototypes and one thing that is beyond frustrating is when using Set Variable and I start type the name of the variable I want to setup, Figma is deciding for me which one I will be setting even if I’m still just typing. For example if I have 2 variables “transaction_info” and “transaction_1”, Figma If I type normal speed, by typing “tr” it automatically sets my variable as “transaction info” which is not the one I want to select. I would ideally prefer to be able to just type it all and not have to use this UI when coding logic and setting variables… but if I have to, could I at least choose what I want to set my variables to?..

I’m experiencing issues with exporting my icons. I’ve never encountered this problem before. When I export the icons as PNGs, they display correctly. However, when I export them as SVGs, they don’t appear as expected. Any advice on how to resolve this would be appreciated. png: ok: svg: not ok:

It’s more consistent than it was years ago, but still: so often I have to Restore default Thumbnail → Set as Thumbnail, then refresh my browser/app on the Files screen to see if it worked. Often it takes 3 to 4 tries for some files

Plugin API: REST API: The reactions data is missing. However, it was normal a few months ago.

I’m using this amazing hack to keep images’ aspect ratio. After the last update, each time I wrap such an image in auto layout, it looks like it affects the internal auto-layout settings.

When I try to only apply the Hugh Content to the width, Figma applies it to the width and height, but I only want to apply it to the width. Does anyone know how I can make it only apply to the width?

Hey there, lovely community! I’ve noticed something quite frustrating since the recent Figma updates, and I’m wondering if anyone else has encountered it too. I seem to be unable to change the font-weight for text inside instances. It always sets to the one that other text has. Changing text font-weight is only working for text that’s not within a component. If anyone else is experiencing this issue, I’d love to hear how you’re managing or if you’ve found any workarounds. If there is a similar issue somewhere, pardon me. I haven’t found it yet. Thanks a bunch!

I have a situation where I have created a component (modal) that I pop using “open overlay”. When I attempt to close the modal variant and navigate to another frame on my page, it does not allow me to. This is causing a lot of frustration as it used to be so easy.

Whenever I paste something in a FigJam file or paste to replace an element, the software makes the element jump a bit, either to the left or right. I only want to replace that element and have the new one in the same place. This leads to me copying and pasting a different tag I’ve created to use on my sitemap, only to see it jumping to the sides and being misaligned with my other elements. This is time-consuming and frustrating to the user.

Hi Figma, REST API is useful and powerful but the speed of it is slow compare to Figma App. Could you fix or improve it? Thanks a lot! Figma App：seconds to show all nodes REST API：much slower than Figma App, may be 5 ~ 20s and more… to get only one node

I am encountering a weird behavior, where child components sometimes resolve the wrong value for a field mapped from their respective child properties. Still, the actual child property has been switched. Example: I have a component that looks like this: The Aa in the upper box is an Icon that is part of a larger Iconography component, which in turn has all sorts of props like size and color. When the Icon is white, it is called “light-vivid” and maps to the “Icon/Light/Vivid” variable. This works everywhere perfectly fine, just in this component, when switching props in the parent (like making the menu left or right for example), the icon’s color gets wrongly mapped to the default color “Icon/Dark/Vivid”. However, the child property is still “light-vivid”: The props: Any Idea why this might happen? Best Sam

I typically build everything within a frame. it’s the most useful element to quickly get things going. I was building a layout that included parallax sections of a page. Each section has interactive elements. I quickly realized that one section that is underneath another section is still interacting with the cursor. Areas of the page that appear to have no interactive elements are working as if they were visible to the view. This is true for even elements that only have simple hover states. If an interactive element is overlaid by another frame or component all of the interactivity of the covered elements should be turned off or disabled until they are visible again. This is how developed experience work, this is how Figma should work. If not this is a major functional flaw with Figma. This is an issue that I have notice for some time (years) and it is still an issue. When is this going to be addressed. This issue wreaks havoc with prototypes for testing and experience demos. This make

Creating an instance of a component that contains another instance that has been scaled breaks the design. See picture for clear walk though. You would imagine that Route A achieves the same result as Route B. This is a bug.

I’ve noticed a bug in Figma, where all Fill resizing fallbacks onto Fixed when changing Layer variables… Is this expected ? It really is a pain a the moment… Anyone having this issue ?