Report a Problem

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:

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.

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 experie

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 ?

We have a design system file that is showing changes that need to be published, for 192 variables and any component that uses those variables. However, neither of the two team members who have access to edit have made any changes. The version history shows a few auto saves over the last few days, but no work was actually done. This is very concerning and we’re not sure what to do or why these would be showing up as changes. Additionally it would be GREAT if the main files would have the same feature that branches do, to show was changed before you publish.

Heya Figma team, Just found this window collision in the new UI. To replicate, select instance > Go to component > Select pen dropdown in Toolbox Cheers!

Figma provides a sidebar where we can assign a “Flow Starting Point.” We can assign them to all of our frames and use the sidebar during presentation to click to navigate to a point. Love that! It even allows for a description of each frame. Great. As you click a point in the sidebar, the check mark shows that is the frame that you have navigated to. Great. However… When navigating through a presentation by clicking interactions within your frames…the sidebar does not follow. By nature, IF I click a link that takes me to a frame that has a Flow Starting Point associated with it, the sidebar should indicate my position by setting the checkmark by the active page. This does not happen. Not great. This leaves viewers looking at a selected item in the sidebar that is NOT the actual frame that they are viewing. Not sure how this has gone this long without correction. I feel I may be the only one detailed enough and OCD enough who uses the

I initially named a variable as background/buttons/primary. Later, this was changed to Cta/primary/default. I updated the variable name throughout the design environment, and the old variable name is no longer present. However, the same component now shows a different variable name in design and development modes. When I changed the color to another value, the variable updated correctly. But when I used a variable with the same color value, it reverted to the old variable name, which no longer exists. Could you please help me resolve this issue? Dev mode:

Hi! Something very unusual happened today: I moved some master components from a file to another, as I have done may times before [cut > paste > publish]. I immediately notice that some of the pasted components were flagged as “invalid” and decided to history revert the changes, after that the trouble begun. Once the components were reverted in the original file, they asked to be published again. After doing that all the instances of those components (both in the same and other files) lost the connection to the master components and asked to “restore component”. When I try to restore the component, the restored master asks to be updated, only to cause the instance to lose the connection again and ask a new “restore component”. An infinite component publishing loop. Furthermore, no matter how far I go in the history, this problem persists and I can’t seem to get rid of it. Any ideas on what could have happened? Thank you very mu

For days now, every time I try to copy/clone an element from an auto-layout and paste or move it outside of this auto-layout, in many cases the element starts to “glitch” and it becomes impossible to drag it across the canvas correctly. Its origin point seems to have shifted, and when I try to move it, the center of movement is not associated with the pointer, but with a position 10-20-30px further away both vertically and horizontally. Moreover, any keystroke (right, left, up, down… any!) to move the element any number of pixels (it could be 1px, 8px, 10px…) causes the element to shift a fixed number of pixels (even in decimals) that has nothing to do with the input given. This is becoming exasperating and forces me to copy, paste, delete, and re-paste each element every time I do this. It’s a disaster… Is anyone else experiencing this? I can’t believe no one else is going through the same problem.

I’ve embedded my Figma prototype in Framer, which is working fine for all viewports in Framer before deployment and in Chrome inspect after deployment in my Chrome (for all viewports) but as I open my site on my mobile the prototype is not scaling properly. here’s my embed code - “style=“border: 1px solid rgba(0, 0, 0, 0.1);” width=“100%” height=“100%” src=“https://www.figma.com/embed?embed_host=share&url=https%3A%2F%2Fwww.figma.com%2Fproto%2Flj0zhz4tMlHcTV3aipmuMC%2FGreenThumb%3Fpage-id%3D1%253A6%26node-id%3D76616-1601%26starting-point-node-id%3D76579%253A4686%26content-scaling%3Dresponsive%26scaling%3Dscale-down%26t%3DHqkiFYSugJZ

I’m working on creating a reusable radio component for my team, and I’m now seeing this weird interaction. I have the variant for each radio bound to a local variable, and I set the Not Selected variant for the other radios when one is selected. The issue I’m seeing is that when the other radios are set to the “Not Selected” variant via this bound local variable, the Text property for the label is reset to the value set in the main component. The expected text returns when I hover over the button to trigger the “Change” to the Hover variant.

Good morning @Figma I am experiencing a bug with Figma’s node API exportAsync when format is SVG_STRING. If you have an image fill and position the fill so its smaller than the containing node dimensions the exported SVG string incorrectly sets the css transforms value for image positioning. This image highlights the issue where you can see the exported SVG as