Report a Problem

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 much in advance!

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%3DHqkiFYSugJZQ3f16-1&hide-ui=1” allowfullscreen>”

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. Is this a bug, or am I just going about this all wrong…?

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 a white area on right side of SVG because the css transforms values are incorrectly calculated. Here’s a link to a Figma design file that reproduces the issue: https://www.figma.com/design/e2y0xU3X5duxDuYbIByacQ.

Hi, I have a branch of the file with various changes to components. When I try to merge it, it tells me that there are some things conflicting with the main file. I go to solve them, I choose to keep all the branch changes and after I apply the changes, the branch just looks like my main file (as if I hadn’t done any changes at all). I restored the branch to a previous version and tried again, no matter what I do, the branch “loses” all the changes that I did. So basically I have a branch that I cannot merge since I can’t pass the “solve conflict” stage.

In this design I’m trying to make it so the animated black text has an animated gradient masked on top on hover. There seems to be a lot of strange behaviors when turned into a component to add the swap instance on hover. In the file you can see the non component animation, the main component, and the instance. Check out the prototype to see how the behavior changes. I noticed a weird behavior that it works a bit better if the main component is in the same frame as the instance. Figma – 30 Jul 24

Am i missing something here or i just can’t create a custom grid size ? Or would it be related to the fact that we can’t create custom presentations with pro plans ? It’s strange since we can have custom colors (the same way Figma design does). Also, you can use different text styles but can’t create your own.

Hi, So for some context, I’m trying to prototype a scrollable overlay on a mobile design to replace a dropdown menu. From what I understood a scrollable overlay is not possible using the overlay prototype option. To achieve that effect I duplicated my main frame and then fixed the whole content in the back, both frames have the same overlay components with different opacity and position to allow me to simulate the move in animation. On my “Overlay Frame” I fixed a component that has 5 variants and to move from one variant to the other there is a drag interaction. The issue is that I can’t use the drag interaction when this component is fixed on the page. Is there a conflict between the drag interaction of a component and the fixed position of that component within the page? I don’t know if that makes sense, here is the link to the file: https://www.figma.com/design/KWIPZkqs4LIUtSEMXSf2PU/Decobec.com---[E-commerce]?node-id=95-2101 Thank you!

Hello! Has anyone encountered this problem? After publishing the library, the connection between components is lost 2024-07-28_17-05-31

So I have Inner and Drop shadow effects added to a shape but the effect doesn’t show when I go to make show my design in Prototype mode? Does anyone know a work around to fix this. This is what the image is supposed to look like. Image should be transparent in the middle. When going into prototype mode, this is what appears.

We have logos in a library file, as well as headers and footers in another library file. The headers include instances of the logo component. We use variables to determine which logo variant is loaded into a header. When using these headers in design files, we find that the logos intermittently load or not load. Is there a Figma loading issue for library images that is occurring? Very frustrating! We had a feature working we thought, and now when stakeholders look at designs, the headers are missing logos. The instance is in the layers tree, it just does not show. To get it to show, sometimes changing the variable to another brand will load the logo in the header within the design. Great, but then as soon as you reload the design file or someone else opens it elsewhere, the logo is not visible again. This is a bug as far as I can see.

Hello everyone, recently we have noticed strange behavior of interaction areas in some prototypes. For example, it happens more often that interaction areas of a button are no longer on the button itself after scrolling in the prototype, but are moved somewhere in the prototype. As a result, the prototype can logically no longer be used as the buttons are no longer clickable. In the attached image you can see the highlighted hotspot box of a button floating somewhere in the wrong place. Does anyone have similar problems and perhaps an idea or solution as to why? Cheers, Sven

I just rolled of a contract project, and Figma’s handoff sucks. I request to better automate and cascade user permissions. Situation: My fellow designer Winnie was taking over my design work I was rolling off from. As part of the transfer, first I made Winnie the Admin of the parent team. BUT as Admin, they did not have edit rights that cascaded down in to the sub-projects and files. Then I made Winnie to full Owner of the parent team. BUT even as the team owner, they were blocked at an at-team level for each sub-project. AND Ownership didn’t cascade down into the sub-projects. As a bug-report / feature request, my expected behavior would be: If a team member is elevated to Admin of a team, or Owner of team, that cascades down into all sub-projects belonging to that team automatically. Thus granting at least edit capability for Admins, and automatically makes the new team Owner the Owner of all sub-projects unless some manual override is done. BUT actual behavior is: Promote team me

Since the recent updates, the autolayout frame resizing functionality has been experiencing issues. Specifically, when switching between horizontal and vertical orientations, all child layers are reverting from their intended “fill” or “hug” behaviors to a “fixed width” constraint resulting in the inner layrs no loner being responsive. This unexpected change in layout behavior is causing disruptions in the overall design production. See Video for example

Nested components are not resizing when the tokens change. When they are not nested, it works well. Do you know how I can fix that? Thank you!

Hi guys, Why is the SAVING TO CLOUD icon near the avatar never go away sometimes? I do have a big file and sometimes I change something tiny and all hell breaks loose. Performance plummets and the SAVING icon and snackbar are always there. Why? How do I fix this? Please don’t roll out new features before fixing bugs, it’s really annoying. My job is to design, not to debug and find bug workarounds. Thank you kindly, Chris

In my main component, I have a state-layer, which has an auto layout applied to it. The frame inside is not absolute positioned. When I jump to my Instance, suddenly the frame is positioned absolute and i can’t change anything about it. This leads to a false behaviour of my components. I guess it’s a bug or am I missing something?

Hi, I’ve noticed that the comments aren’t moving along with the frames in Figma. I have to manually move them each time. I’ve tried closing and reopening Figma, but the issue persists. Is there a way to fix this? Thank you.

When working with complex nested layouts, especially auto layouts, I routinely need to move things around, add children to frames, or rearrange elements on the page. As such, I may end up copying elements (components, frames, etc.) onto my clipboard. When it comes time to paste the element, I can traverse the layers panel to find the parent container where my pasted element should appear. Once I select that parent node in the layer panel, when I paste, the element will appear in a predictable place - as the last child of the node I selected. However, I often need to add a component from a library. I usually do this through the resources toolbar (Shift + i). My expectation is that the inserted component would follow the same logic - inserted as the last child of the node I selected in the layers panel. However, the placement of the inserted component seems random. Sometimes it appears as a child of the element selected in the layers panel, other times it’s inserted into seemingly random

When my app is not in full screen mode the mac controls (close, minimize, full screen) sit on top of the tabs I have open. See screenshot. I am running the latest version of Figma.

I used to be able to hold Option in Design Mode and see the measurements between items that were selected and hovered on. This is a huge timesaver for me and my design workflow. I hope this is just a bug in UI3 and that it is not planned to be removed.

The latest Figma after config, no longer hides the selection rectangle when adjusting the stroke. So you cannot see what the stroke adjustments are. One of the top features of Figma from day #1, was you could see what you actually were adjusting. Notice the blue selection rectangle? How am I supposed to see the stroke while adjusting opacity? I have to guess 😦

Is anyone having trouble using the Figma app? It stays forever on this screen for me. I already tried restarting my iPhone, reinstalling the app and logging in/out, any ideas how to fix it?

I believe this is similar to a bug reported here: GIFs not available in the API - #5 by Gleb I’ve also highlighted it in the Figma Developers slack here: Slack Reiterating it here for ease of context. I’ve recently discovered a bug where where existing gif content isn’t being detected as a gif, and they do not play in prototype mode. I’ve managed to successfully reproduce 3 different scenarios for this bug: Copy the source asset (it was previously detected as a gif, but now is an image) into a fresh file + frame. It is detected as a gif, and plays as a gif, as expected. Copy the source asset into a fresh file + frame. Paste the asset in, again. First target is detected as gif, second target detected as image. Both play in prototype mode (consistent with the UI bug reported). Following up from scenario 2, if the FIRST TARGET is removed, the second target no longer behaves as a gif. Same issue happens when it’s done programatically with createImage , whether it’s with a new fill or a