Report a Problem

Exiting the group from the file doesn’t work, it still exists. Is there any way to clear/share the record of the file?

This week I had many problems with the auto-layout. The hug auto-layout with padding in components seems to have an unstable behavior. On my recording you can see the problem, I enter 16px of padding top+bottom, and it disappears on bottom when I change the text in my instance. FYI the font I use is a Google Font, that is not supposed to bug. Please solve this problem, it is extremely restrictive 😭 I went back to the old UI because I thought that the problem came from there, but it’s not. Sorry for my English, I’m French

我有2 个 Figma 账号，现在我发现这两个账号主页左侧的项目展示上完全不一样，如何恢复到旧版样式？

Hi, I created a dropdown component. When the first option is selected and then I try to change it to another option, the first option gets chosen again. Can someone help me?

Now i always have to clear cash and restart the app, and configure each setting anew each time, I thought the problem was in the computer, that there was perhaps some kind of failure, but now it is systematic, I correlate this with the update that you somehow made this summer, during your presentation, now I understand that while your engineers were working on new functions, in particular with the autonomous layout, they made some kind of mistake, because of which everything that I have in the layout is now added for x is “fixed” and y is “hug”, all the time i made layers autolayouted… Can you please fix it? I always have to clear cash and restart the app reconfiguring everything from scratch every time it is tiring… Working with autolayout is already very difficult, it would be nice if instead of automation you would focus on eliminating errors that your new solutions cause due to the still existing old ones I’m sure I’m not the only one with a problem with the app. Since I contacted

Im not sure if this is how it’s meant to work but having a complex component with other components with it have been used to hide some of it. Though in dev mode all components are visible in the side panel although hidden in the display. We teach our devs to explore the side panel to check component structures and this adds a little caveat in the discussion. So should the side panel visuals be the same as design mode and grey out a component section while its hidden, or reveal it like in dev mode?

In the new Figma UI the toggle button for properties in a component isn’t fully clickable, only a certain area of the toggle is clickable. This is happening to me in the browser version of Figma. Small thing, but annoying that I have to click in exactly the right area of the toggle.

Since the new update, when I add auto-layout to multiple (2+) art boards then add padding to the auto-layout, it shrinks the art board width. I don’ know if this is a bug, or some new feature I’m not aware of, but it messed up a lot of my work and cost me a lot of time. If there’s a way to turn this functionality off, someone please let me know. If this is a bug, devs please fix this as soon as possible. Thanks

For the UI kit Figma file, we have a header which is a component, and a Section frame containing the components for each component family. We group these to together so we can arrange them in the page and ease of resizing if required. However when these two are grouped together, you cannot leave annotations. Is this expected behaviour?

I’m having an issue where my prototype mode isn’t displaying some of my elements. The design looks great on my Figma page and is all on within the same frame but the prototype mode doesn’t display it. I found a couple of old threads talking about this same issue but it doesn’t appear to be fixed. Component instances are missing elements when I run the prototype Ask the community Trying to find a solution to this problem, I found that users have elements missing when running prototypes from imported Sketch files or have lines not displayed that are .5px instead of 1px. These are not the problems I am having. I have two Figma projects with prototypes that have been stable for 2 months. When I run the prototypes and activate dropdowns, modals and popups elements will be missing within them. I check the layout files and all elements are there. Examples are checkboxes, for… Missing elements while presenting Ask the community Hi,

Actual behavior I have to fiddle with my cursor position if I want to select Collection 1, because the option spans across the top edge of the Variables dialog and the UI is allowing me grab the top edge of the dialog through the collections list. I’m able to resize the dialog and leave collections list open. Expected behavior I’d expect that I shouldn’t be able to interact with elements behind the collections list.

If you are using the export function and want to create PDFs you might have the problems that some frames will not be printed or some PDF has issues. When using Adobe Acrobat to print it seems that this is not a problem, somehow Adobe solves it. But if you are on a Mac and you use the Preview to open the PDF and print your PDF will not be printed correctly. Of course, I want to create PDF that can be printed by everyone no matter what device or program is being used. Many have thought that the missing frames or images is due to the PDF using RGB colors and not CMYK and some of us have like me tried different plug-ins. But I would say it has probably nothing to do with that. I am not sure it’s a bug in Figma or a bug in the Mac OS X preview… but here is my advice to avoid the issues: if you have a frame with clipped content the image inside the frame might not be printed at all. Make sure to unclick the checkbox, sometimes if using SVG they could contain of multiple frames and clipped

Hello! Random objects on my file will appear with an outline, as if someone has selected it. This happens even in a new file where the only person is me. I’ve been able to replicate it when I create two circles and add a mask over it. My files are haunted 😦

Sorry for the quite awkward title, but, here is the thing … One of my Figma accounts the UI has been promoted to the new version. Yeah! Very cool UI, I’m so happy. I find it refreshing, functional and easy to switch my behaviors on. I think there is a small (but maybe not so small) issue with those sidebars. While the previous UI sidebars touched the window borders now they float within some pixels from the borders. I saw that Figma UI guys decided to apply some kind of blur behind those sidebars, like to say “hey, this space is not really available to you user, please drag or zoom out the canvas”. Cool, but … maybe you Figma guys forgot some situations in which elements hidden by the bars are still active and receiving events from the user. A couple of examples: if I drag a prototype connection the canvas starts to scroll when, while dragging, I reach the side of the window. This means that if there are some elements hidden behind the sidebar the connection will stick to them but I

I started a new flowchart from a template and decided to change the color of the shapes. However, I can’t adjust the color of the border or the text inside the shape. Worse, if I simply copy the color of the default template shapes and paste on a new shape, the border has a different color and the text is always black. In the screenshot below, the shape on the right is the original one. I simply duplicated it and pasted the same fill color code (#F1E5FF in this case), but the border color is obviously different. And it seems there’s no way to manually change the text color… If I change the original shape into a different shape the border color will also change and I can’t ever get the same border again. Is this a bug? How can I create a box with the same colors as the original shape? Why can’t I create a purple box with purple text, or green with green text, etc?

Recently I am facing below problem with the professional plan. Users without team permission (view, edit, etc.) are not shown in the Members list In case they don’t show up in the members tab but need edit permissions for Figma or FigJam, it is necessary to grant first Team Permissions. A few months ago this problem wasn’t there yet. Also, I noticed that only one part of the users are not shown (couldn’t identify the reason yet). These users can have edit permissions for Figma or FigJam while not having team permissions. I would like to know the following: if this is this a bug as it hasn’t occurred before how to give a person edit permission for Figma/FigJam without giving team permissions Thanks in advance.

This is the second time this has happened to me. I have spent a ton of time updating my variant components to work in my prototype. Mostly mouse over interactions. I test like crazy as I am building. I test in the component library files and I test in a copy of one of our prototypes. While I am building things are working great. Later in the day, I restart Figma, then go back to the same prototype, and just about all of the interactive components stop working. I have tried opening up the prototype up in both the desktop (Mac) and the web version of Figma but neither are working. I tried several restarts and reloading of the prototype but nothing work. Now one thing I did notice, one of my co-workers was in the prototype. After he left all the interactive components started to work again with one exception. All the components that include images (i.e. avatars), the images are not showing up. Anyone else experiencing this or similar issues?

I just noticed something. If you have a resource/file in the community and some components are in a different mode (i.e using another set of variables) e.g a different theme or dark mode, its visually breaking. This is frustrating because people wont know this is a bug and assume the creator made crap. Is it me? Is there something I didn’t do correctly? Take a look at some examples below or See the issue live yourself (this isn’t an Advert please) Example one From Figma preview box 👇 From inside the real file 👇 Example 2 From Figma preview box 👇 From inside the real file 👇 There are many more examples. See the issue live yourself. Is there anything I can do to fix this or is this actually just a bug

Desktop App version 124.1.16 (UI3) When changing auto layout direction, it incorrectly sets the container to hug contents instead of fixed which causes the children (card) to be put to fixed causing unnecessary steps to fix. These are the properties before changing the auto layout direction: This is the current result: What it should be: This is an extremely annoying bug and makes working with auto layout more annoying than needed. This was fixed for a couple of months, but the recent updates have reverted it back for some reason.

using the K shortcut to scale will impact corner radiuses within a component at the same rate as the dimensions. (as expected) This can be done to nested components where initially it works as expected. when overriding the nested component instance to another that also contains rounded corners the “scaled” attribute seems to get lost and the rounded corners default back to their unscaled values.

As the bug topic states, I’m unable to apply a variable that is aliased and has multiple modes. I am able to apply a global variable, with no alias and no modes - but that doesn’t help me with theming between different modes where the component has a different height depending on the brand. Can anyone help me troubleshoot this, or submit this as a bug to the appropriate team? Below is the screenshot of the variable that I’m attempting to apply, and no - it does not have scoping attached that may prevent it from being applied to the height of the component. Below, is the screengrab of trying to apply the variable to the component. It does not appear in the search and I have confirmed that the token has been published. As you can see, I am able to apply a global token - which is not entirely helpful as it doesn’t do much in regards to theming.

Can we please fix this to see full properties full names

Hello, I am trying to apply grid variable using below code by following Working with Variables | Plugin API guide. Error : Expected “layoutPattern” to have type “GRID” but got string instead We are trying to create a copy of layoutgrid and apply new variable using below code let propCopy = [...node.layoutGrids]; propCopy[0] = figma.variables.setBoundVariableForLayoutGrid( propCopy[0], "gutterSize", variable ); node.layoutGrids = propCopy; propCopy[0] is as below {alignment: "STRETCH", boundVariables: {offset: {…}, sectionSize: {…}, count: {…}, gutterSize: {…}}, color: {r: 1, g: 0, b: 0, a: 0.10000000149011612}, count: 4, gutterSize: 20, offset: 100, pattern: "ROWS", visible: true} But after executing, we are getting below error: in setBoundVariableForLayoutGrid: Expected "layout…ttern" to have type "GRID" but got string instead mesage: "in setBoundVariableForLayoutGrid: Expected "layoutGridCopy" to be one of the following, but none matched: \n Expected "layoutGridCopy

Hi Figma Support Team, I’m experiencing an issue with the “Copy and Replace” keyboard shortcut in both the Figma Desktop App (version 124.3.2) and the web version. The shortcut has stopped working on both platforms. I’ve already tried restarting my computer and the Figma app, but the problem remains unresolved. For additional context, my computer is running macOS Sequoia 15.0 Beta. Could you please provide guidance on how to fix this issue? Thank you!

I am trying to show the hidden box using a boolean variable but the problem happens when I apply the variable on the instance which will change to another variant of it using the time delay, But that change of the variant to another variant is not happening in the time delay prototype but if I give the on-click to change to the other variant that’s work. not sure what is wrong with it. Attached is the Figma link Figma – 25 Apr 24