Report a Problem

Hi all, I got an error about component variant does not work properly with shape rotation. I created a component with a shape, then I add one more variant (rotate 45). But it does not work as expected. I have tried both Figma Desktop version 116.3.6 and web browser version. Have got the same error?

In our design file, when view users, like developers or product owners, view a file, items, vector graphics, variables, etc. Will not show in the file. They are like a ghost instance of the component or visual. It is there, but it’s liek the data is not loading. I had a similar ticket, where we had a product owner “regenerate the instances” and it seemed to help, but we have some users who cannot run quick commands due to access, so we need something that is more of a permanent fix, since we can’t ask every viewer to run the quick command, and it doesn’t seem like the command is working across users for the same file.

is anyone else experiencing locking/freezing on large files? Scenario - Brand system for enterprise size company with multiple shared libraries. File opens fine however specific pages freeze. No telling why. Memory usage for that specific page is less than 30% and takes around 5-8 mins to open if someone has a fix, that would be great

I’m using Figma batch export all the images, the export setting is jpg but end up with pdf My setting end up with pdf

I found that arrow key navigation is not supported in some dropdown of UI3. Is this a bug or intentional?

Whenever I try using copy/paste in Figma it’s a gamble if the copied frame, or components will actually be copied and pasted correctly. Here is the common issue: Select an element > cmd+C > go somewhere else in the file > cmd+V Now about half the time it pastes something that was previously on the clipboard instead of the thing I just copied. It’s really frustrating and sometimes takes multiple attempts to copy paste something. This has been an issue for at least 2 years at this point.

I’ve created a component. I wanted to draw a line within the component, much like adding a line of text inside a component. The resulting experience is utterly weird. It draws points that are out of my view and gives me multiple lines. Video attached to show whats happening. It’s probably something very few people would do… first time for me…

In the documentation for figma.on, it lists The plugin has started running. twice.

We are noticing in the last week or so that our autolayouts get jumbled and need to be regenerated to work again. Please see the following video: Figma Autolayout Bug

I’ve been setting up a library of variables across multiple platforms we design. For some reason, any adjustments i try to make on this one variable causes the entire file to freeze and i have to close/reopen to get back in (and the change doesn’t stick). I can’t even delete the variable or the group it’s in without a freeze. Anyone else encountered this issue?

Noticed one of our files is showing what looks to be en/em space, but cannot batch replace these since Find and Replace does not work with spaces, whether is single, en, or em space, etc. This is a case where hidden type characters could also be useful to identify the issue. Suggestion: Make Find and Replace work with invisible characters (single, en, em spaces, etc) Ability to show invisible characters in text layers

Over the past three days, attempting to swap an instance or insert the component has resulted in the menu for each of these actions loading indefinitely, regardless of whether I’m using the Figma app or the browser. I have not found a solution to this issue, and it is now impossible to swap an instance within a component. I am unsure why this is occurring, as the same file was functioning properly four days ago, but suddenly none of my assets will load anywhere.

One of my most used keyboard shortcuts seemed to stopped working: Command + Right-click on an object to quickly select a child layer. After some troubleshooting I realized that this happens when “Right-click and Drag to Pan” setting is enabled. I like both of these features, and they should not be mutually exclusive. Can this be fixed?

figma bug what is this…?

I set the element width to fill in an automatic layout. When I change the direction of the auto layout, the element width becomes a fixed width. I have to set the width of the element again. I hope that switching the direction does not affect some of the settings of the original element, otherwise it will cause a series of extra work.

Reposting this as a bug since it isnt tagged as such, and years later it is not fixed: Link to nested frames Share an idea I asked the developer and there is a workaround. Instead of using the large blue share button top right, find the nested frame you want to link to in the layers panel. Then control-click, select Copy/paste as > Copy link. The link that gets generated then links to that specific frame. Hooray for Anders the developer!

I’m not sure if I don’t know how to use the ruler in the new Figma UI or if it’s a bug. I searched about it and tried a lot of ways and couldn’t get the ruler to work in the new Figma UI.

From what I’ve seen, this still seems to be an issue in UI3, as well.

Everytime i want to scroll to the bottom of the right sidebar (Which is floating in UI 3) i always end up scrolling the artboard instead of the sidebar / menu, as i have this habit of taking the cursor to the extreme right of the screen and then scrolling (Habit carried from the UI2), and everytime this happens, my flow state is broken and i have again carefully take the cursor inside the sidebar and then scroll. I understand the logic behind this change, but keeping the areas besides the floating sidebar interactive has no use, the only important section in the centre of the artboard.

Hi there, I would like to express my thoughts if this is a bug or not. I am using current version/release of Figma, and my organization is using Pro plan. I created a new collection, and this is the 20th collection in my UI Library. When checking in my project, there’s no indicator for updates from the Library, even if I tried checking it on actual implementation. Like to select what Action then select Collection. I badly need help for this asap. I hope someone here can help to discuss further the issue. Thanks you in advance!

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.