Report a Problem

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.

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!

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?

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

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.

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?

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

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?

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.

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

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.

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

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?

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

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:

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?

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

Whenever I drop screenshots into my branch file and then merge the branch all my image fills disappear. The frames, groups and images are all still there, but the image itself is not visible and image fills disappear.

Hi there. I’m developing a Figma plugin. When I try to export some frame, my plugin gets crash. And stack trace does not help me. (Stack trace is below) Error: Saving the document at N (figma_app.min.js.br:1467:29637) at G0s (figma_app.min.js.br:1469:1154) at IO (figma_app.min.js.br:1469:1109) at figma_app.min.js.br:2541:98036 at figma_app.min.js.br:2541:98477 at figma_app.min.js.br:2536:203277 at figma_app.min.js.br:2536:103365 at figma_app.min.js.br:2536:116123 at figma_app.min.js.br:2542:131589 at figma_app.min.js.br:2542:37642 at figma_app.min.js.br:217:3979 at figma_app.min.js.br:2536:199619 at figma_app.min.js.br:726:365680 at figma_app.min.js.br:2542:93677 at figma_app.min.js.br:2536:55857 at e6 (figma_app.min.js.br:1686:27317) My plugin does not care about exporting things. So I’m stuck in this. Does anyone have some advise? Thanks.

I get the following error when I try to update my Figma community file. I tried all the files posted on the community and got the same error. what do I do? Error message: hub file image not found

As soon as CONFIG was over I was the only person on my 22 people team that signed up for the UI3. And yet, nowadays almost all of them have it and I don’t. I feel that the sign up was only for show and it’s making somehow frustrated since I really liked the new UI (I have been using on my personal account, which, should I say, also did not sign up for it 😦 )

I’ve got a table component where the first column is always fixed and the rest of the columns can drag left (“under” it). As soon as the dragging starts, I show a drop shadow effect under the right edge of the fixed column. When the user drags all the way back, the drop shadow disappears. This all worked perfectly yesterday. Today I notice that the user can only drag an inch to the left before the drag interaction stops. This leaves several columns still clipped off to the right. Also, the drop shadow does not appear. THEN, if I start another left drag interaction, the drop shadow appears and it lets me drag a couple inches past the end point such that I have a blank spot after my right most column!

Although I removed library component, it still alive in assets panel in files using library. Why? i tried to remove it (to restore and re-delete component again), but it still there. it seems like ghost/zombie component that never can be removed.

I have quite a big file with many components in use for table cells, buttons, form elements etc, and have been using Interactive components for link / button hover states, check boxes etc. My prototypes were working well until the last update. Now during random parts of the flow, my prototype randomly jumps between a series of screens, making the prototype unusable. I went though all pages & elements, checking I didn’t have any stray ‘hover’ or ‘after delay’ actions in place and they were not any. I did however notice that some flows were fixed, by changing some duplicate frame names I had. The issue would however, pop up elsewhere in the flow and could not be fixed by adding unique frame names. The only thing that stopped the bug, was when I turned off ‘Interactive components’ for the prototype. The prototype then worked fine after that (minus my micro interactions). Bit of a strange bug, but thought i’d share for investigation.

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?