Report a Problem

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?

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.