Skip to main content

Report a Problem

Experiencing issues? Report them.

  • 2,207 Topics
  • 6,001 Replies
2206 Topics
Ojanti
Ojanti
asked in Report a Problem
Components with Figma's `mode` variables are visually broken in the preview box of a community file 🤦‍♂️

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

2555
djv
Figmate
Zach_Thomson
Zach_ThomsonNew Participant
asked in Report a Problem
Auto Layout incorrectly sets container to hug instead of fixed

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.

86416
djv
Figmate
Wolf_Boese
Wolf_Boese
asked in Report a Problem
Instance override scaling corner radius

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.

820
Wolf_Boese
Cody
Cody
asked in Report a Problem
Unable to apply aliased variable to height of a component

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.

312
Cody
Arthur_Baracand
Arthur_Baracand
asked in Report a Problem
Component properties names are cropped

Can we please fix this to see full properties full names

101
J
Figmate
Figterate
Figterate
asked in Report a Problem
Getting error in setBoundVariableForLayoutGrid

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

1752
M
Yu_Liu
Yu_Liu
asked in Report a Problem
"Copy and Replace" Shortcut Not Working in Both Figma Desktop and Web App

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!

250
Yu_Liu
Admin16
Admin16New Participant
asked in Report a Problem
Not able to use the variable

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

64529
jhingrhed
iammai
iammai
asked in Report a Problem
'Change to' with conditional action not working

When based on a conditional I want the component variant to change to another one (depending on the conditional), it doesn’t let me choose it to go to two different change-tos. If I change one of them, it changes the other one immediately. I would upload image or video but I can’t as I am a new user. But basically to replicate this: Create 3 variants of a component (eg a number 1, 2, and 3 in a frame, and make them into component variants, let’s say the prop is either 1, 2, or 3) Create a variable (eg. next that is 3) From variant 2, create an on click interaction that has a conditional: if (next == 3){ change to props = 3 } else{ change to props = 1 } What you will see is that when you create the second change to, it is automatically set to props = 3, and if you try to update the second one to props = 1, it will change the first one to props =1 as well.

656066
Justin42
Noah_Kroes
Noah_Kroes
asked in Report a Problem
BUG: Auto-Layout Adds 90 Degrees Rotation

Hi Guys, I am currently experiencing an annoying - what seems to be a bug. Whenever I add auto-layout, it adds a 90 degrees rotation. To the whole frame and to all the child objects. I can’t wrap my head around this, it’s super annoying. It happens every time in this file with auto-layout, even when not working with components or variants. Happens with ‘clean’ objects as well. In the screen recording I tried to make it visible what I am experiencing. Is there anything I am doing wrong? Would love to hear some feedback or people who experienced the same thing!

10568
Katharina_Blust
Valentina_Mendez
Valentina_Mendez
asked in Report a Problem
Can't click to adjust constrains

For 2 days I have been having issue with changing the constrains. I can’t click on the select/dropdown, and only sometimes can I select a location on the illustration, but this is not always the case. I wonder if this is bug caused from a new release?

941
y_toku
Figmate
Matt
Matt
asked in Report a Problem
Typography issue in scaled instances

I run into this exact issue all the time and there is no permanent fix, type will revert to real size in scaled instances which makes design look broken, only “solution” is take a screenshot and use that or detach instance, both of which are of course not that helpful Same issue as here Problem with scaled instances - #5 by Nina_Magomedova

311
y_toku
Figmate
Adam_Olin
Adam_Olin
asked in Report a Problem
Bug: Selected colors modal get stuck on cursor move sometimes

Sometimes when I come to change on of my selected colors with a new varible color the dialog get stuck on my curser and I can only get out of it by pressing or pressing esc. If I press the mouse it selectes the color under the one I want.

61
y_toku
Figmate
Pav
Pav
asked in Report a Problem
Bug, or a file that's too big?

Hey community, I have a Figma file that’s in a branch, and I was going to merge it today to enact changes in our design system, but I’m having some rendering issues. Parts of frames appear missing, and when I click into them some elements reappear, some remain hidden. I tried to close the file, tried to restart Figma, and nothing seems to be sorting it. It’s a huge file, so re-working it from scratch would be a nightmare, so my question is - has anyone encountered this bug? What can I do to sort it?

634
y_toku
Figmate
tank666
tank666
asked in Report a Problem
Interactive component animation stops when opening overlay

Creating an example for this topic, I found a bug of stopping animation of an interactive component when the overlay is open. Expected result If the animation of the interactive component is in progress, and the overlay is opened at this time, the animation of the interactive component should not stop. Actual result When the button shows a loading animation, an overlay appears on the frame, and the button animation stops until the overlay is closed. Additional information Prototype:Figma – 4 Mar 21

23186
Rolka_Luke
E
Eugene_Hoban
asked in Report a Problem
Trade Gothic Next LT Pro, Base Line Shifted down about 2 px

Anyone experienced base line shift bug within Figma, I can’t find a way to fix this. Installed Trade Gothic Next LT Pro Applied the font used underline Underline is overlapping the font (this is where I first noticed it but it appears anywhere the font is used). This specific font seems to be shifted down 2px. when I change the font the baseline goes back to normal on the selected font. It is only Trade Gothic that I am having an issue with. It is an official Adobe font. Any suggestion on how to fix this?

1943
E
Alamaki
Alamaki
asked in Report a Problem
Hidden layer editing bug

On UI2 maybe UI3 too, hidden layer always shows as having fixed state, and you can try to set it to fill or hug, but it always goes back to fixed. This seems like a bug of implementation details leaking into the UI. Habituated users are not going to toggle layer visiblity just to change something that trivial. Then they’ll likely not notice when a change they made got silently reverted right, so time gets wasted on debugging. It should be possible to set properties of a layer without making it visible and the UI should view the layer’s properties as they are set, not what layer hiding implementation uses.

210
Alamaki
Joanna_Tajs-Kusmierek
Joanna_Tajs-KusmierekNew Member
asked in Report a Problem
The link to the selected frame does not work for me

Hello, the link to the selected frame does not work for me the topic concerns links generated since yesterday (or at least I noticed it yesterday); previously everything worked as expected the links generated earlier lead to the correct pages as expected currently generated, regardless of selection, they open the first page of the project I restarted the program; I tried the application and the browser version on different browsers I would be grateful for tips on what else I can do with it? this is an incredibly useful feature Regards Joanna

1272
J
Figmate
rwb_marns
rwb_marns
asked in Report a Problem
Figma: if/else navigation bug

I am trying to create an if/else navigation based on login state. Upon executing the feature, I noticed that the bug happened 4 times. See attached video After clicking the refresh button, and continue the prototyping, it will work. However, in your next attempt in other component/element, it will happen again.

337
rwb_marns
Jakob_Engelbrecht
Jakob_Engelbrecht
asked in Report a Problem
Figma's RGB color values seem to have a rounding error?

It seems to me that Figma’s RGB color values are slightly off / have a rounding bug? As mentioned in issue 10852 Figma’s RGB color values are in the [0, 1] range, whereas web RGB is in the [0, 255] range. If that’s true, then multiplying the Figma value in the [0, 1] range with 255 should produce a valid value within the [0, 255] range. And similar dividing a web RGB value in the [0, 255] range with 255 should produce a valid value within the [0, 1] range. But doing that doesn’t actually produce the correct values? E.g. going from a web RGB value of [229, 241, 251] to Figma RGB should yield: [229, 241, 251].map(val => val / 255); // outputs => [ 0.8980392156862745, 0.9450980392156862, 0.984313725490196 ] But querying Figma on a node with that color fill yields: figma.currentPage.selection[0].fills[0].color; // outputs => { r: 0.8980392217636108, g: 0.9450980424880981, b: 0.9843137264251709 } Comparison: r / 255: 0.8980392156862745 r (Figma): 0.8980392217636108

10616
Evelyn_Hasama
Figmate
Universalnick
UniversalnickNew Participant
asked in Report a Problem
Scaling frame or variant component area lagging

Hi, recently Figma started lagging when i’m trying to change the width/height with the mouse of any(not empty) frame or component area. Any of you had this kind of problem and know how to make it right?

251
djv
Figmate
Elyriades
ElyriadesActive Member
asked in Report a Problem
Horizontal slider doesnt work with vertical scrolling in figma mirror

On drag doesnt work in Figma mirror. Its working broke, you should fix it

443
y_toku
Figmate
Garrett_Campagna
Garrett_Campagna
asked in Report a Problem
Keep Branch / Keep Main buttons only appearing in Browser

I have an issue where i’m only able to merge branches and resolve conflicts in the browser as my Desktop app doesn’t show these buttons. Any ideas? Browser screenshot: Desktop app screenshot:

272
y_toku
Figmate
Tascha
TaschaActive Member
asked in Report a Problem
Can't change variable mode of instance in other file

New day, new bug 😅 So I opened my file 1 today to find that I can’t change the variable mode for some of my instances - this is true for instances that come from file 2 and have variables attached that come from file 1; the button just stays stuck on the clicked state but the dropdown does not open. in file 2; correct behavior of the variables mode selector. the variables are from file 1 (“Tims master components”). in file 1 (“Tims master components”); button stays stuck on the clicked state but does not open the dropdown… For items that have other variables attached that are working it just does not show this specific variable mode (but it should!), like so: here I should have the other set of file 2 (“2 states”) also displayed, since inside are instances that utilize variables from this file… Last week this was still working btw withouth any trouble. I already cleared my cache and restarted Figma without any changes 😔 Any ideas?

220
Tascha
Renan_Malato
Renan_Malato
asked in Report a Problem
Manipulate Elevation of a Layer / Drop Down Menu Case

When you have a form with Drop Down menu / Autocomplete fields with autolayout, the layers list order determines the position of a layer in your form, not the elevation So when you click to dropdown the field, the dropdown goes - in the back of the below layer The way I find to hack that is creating kind of a Position Absolute Wrapper for each line and then reorganize the layers to make that appear on front This is so weird and tricky and takes a lot of time everytime I have to do this. I believe a simple Elevation zIndex Control when is set to autolayout would solve that for us Please, Figma! The way Figma now arrange layers layout is - what is below is above

411
Eldurini
Terms & ConditionsCookie settings