Report a Problem

Hey all, seems like there are similar shadow effect issues in the prototype but I don’t see anything resolved. I have a shadow effect that works perfectly inside the design file, but in prototype present mode, it looks completely different. Some of the shadows seem fine…which adds to more confusion. Does anyone know why this is, or which visual representation is correct?? In design:

In the “Local Variables” tab, when the list of variables becomes lengthy, the “+ Create Variable” button at the bottom ends up obscuring the last variable in the list. This can be quite frustrating because there’s no way to scroll down, leaving the last variable hidden behind this button and inaccessible. How can we address this issue?

Hello everyone! I’ve been working on a Codegen plugin for my team. It takes a group of elements and exports them as a React component. Everything seems to be working perfectly, including its display within the FIGMA interface. However, when I copy the generated code and paste it elsewhere, I notice it has double the intended indentation. Instead of the expected two-space indentation, it’s coming out with four. Is there a setting or solution to address this? Thanks in advance! Marlus

Is anyone having issues using Content Reel? Every time I try to use it, it locks up the Figma Desktop app? Same behavior in the browser as well.

When I select any instance in any file the name of the instance does not appear correctly in the design panel. They are all labeled “Document”. This just happened, never came across it before, so I’m guessing this a result of the latest “update”. It makes it pretty difficult to know which instance I actually have selected and am currently working on since they’re all named the same exact thing now. I can see the true name in the layers panel, but that’s not where I’m making the changes. A quick fix for this would be greatly appreciated as naming conventions are kiiiiiind of important.

I use links to share designs quite often, however recently it has stopped working like it used to. When opening a link in mode=design it only selects the frame/component. It does NOT teleport you to it. However, if you change the links mode to mode=dev, it selects AND teleports you to it. I assume this is a bug because it used to have the same behavior for both modes. I also have open-in desktop app enabled and I haven’t tested it to see if it does the same thing opening in the browser.

I’m having issues with variables being retained in my prototypes. Variables continue self-deleting on their own. I haven’t nailed down on recreating the bug yet, but from what I’ve noticed is that when moving frames, with variables linked to components I have created, to another file, these variables get deleted when moving the frame back into the original file. I’ve looked in all my collections to confirm my concerns, and the variables are indeed missing. I have created multiple full-fledged prototypes, applied variables, and then these variables get removed mysteriously - including their associated groupings - brings concern to me and is urging me to stop creating in-depth prototypes with variables.

I am encountering a bug in Figma where some images in the preview link appear to be rotated 90 degrees when viewed on mobile browsers. Steps to Reproduce: Open the Figma preview link on a mobile browser. Observe the display of certain images. Note that some images appear to be rotated 90 degrees. Desktop and mobile preview Environment: Figma version: Figma Desktop App version 116.5.18 Mobile device used: iPhone 11 Mobile browser used: Safari (iOS 16.3)

Hello, I have got trouble with how Figma handles the CSS variable name when it ends with a number. Please, look at my screenshot. Variable “c1 500” must not be “–c-1500” Am I right ?

The scenario is really simple. I have a button component with two icons (at the sides). But the icons are hidden. If I select the button and I want to change the font color from the palette colors, it only applies to the visible content (in this case: the text). So if after changing the color, users want to make the icons visible, these icons have the old color

I often make a selection, and use the return key to drill down into a component to select elements – this no longer works. See video where I enable the icon, and with the component instance still selected, I hit return and the toggle is focused.

Just recently when using either the freeform scale tool with K or via the scale panel results in the item completely breaking or not honouring what values you enter. Im noticing this now when resizing component instances Seems fine when I detach the instance. This used to work just fine, but seems after a recent update instance scaling is broken?

I continue to use styles with a sole purpose of image fills and gradients since this is not applicable to variables and truly does not make sense to move to, these fills are for easy access to a gallery of images for our designers to choose from without having to open another application like Unsplash. Only problem/bug I am facing is not being able to see the image fill in the styles dropdown or even the local styles panel when they are created and published. Thus making it hard for our designers to know what they are choosing. Has this occurred to anyone else in the last update? Today, I updated to version 116.13.3 and am seeing the issue. Thanks!

Hi! I’ve been trying to find a reason for the following behavior but I can’t either fully understand the property inheritance logic or there is a bug in how properties are inherited from within a deeper component structure. Figma component property inheritance issue I have set up a button component using a base subcomponent that defines the states (default, hover, active), interactions between states, and styles (default, primary) of the button. Then using this as a base I have the master component that defines the type of the button (text, icon or text + icon). The master component has some overrides to the state component like custom padding on the icon butto

It seems variable properties are undefined on SectionNodes, despite being documented and available in the typescript typings. for (const node of figma.currentPage.selection) { if (node.type === "SECTION") { console.log(node.boundVariables, node.resolvedVariableModes, node.explicitVariableModes); } }

I have created a component for a realty property page, inside it has nested components with an auto layout. There is a read more button that when pressed changes the information from one state to another that shows the whole paragraph of text. This works fine before making into a component, works fine as a component, but the second I drag it out of my assets the auto layout no longer expands in height to make room for the text and instead places the text behind the next section of the auto layout. Hopefully I have made this clear, I am still learning and starting to delve into the more complex side of Figma.

I’ve created a boolean shape inside a frame with separate constraints for its two components. Resizing the frame manually/numerically works as hoped, with the rectangle scaling to fill the frame and the circle remaining pinned to the upper-right corner at a fixed size.

I created a vector using the figma plugin api accoding to the api docmentation and refered to “the subset of the SVG path format part”. But got the error message of “in set_vectorPaths: Failed to convert path. C is not a valid first command at VectorNode.set_vectorPaths [as vectorPaths]” and "“in set_vectorPaths: Failed to convert path. Q is not a valid first command at VectorNode.set_vectorPaths [as vectorPaths]” "

Pretty self-explanatory, but I would expect a “documentchange” event to fire when the Document’s name changes, but it doesn’t. The even fires when a layer’s name changes, as well as when a page’s name changes. Would be great to see this added 🙂

Hello Figma Team, I hope this message finds you well. I’d like to report a potential bug in Figma’s DocumentChange event. After some testing, it appears that this event is not triggered when changes are made to the indentation or list options of a text node. Here’s a step-by-step guide to reproduce the issue: Start a Figma plugin. Attach an event handler to the DocumentChange event using the following code: javascriptCopy code figma.on('documentchange', console.log); Create a text node and select it. Change any property of the text node (e.g., text content, font size, color, etc.). Observe that the event handler logs a message, indicating that a document change has occurred. Now, select a portion of the text within the same text node and apply list formatting (e.g., turn it into a bulleted or numbered list). Notice that the event han

1. Describe the bug/issue you’re running into? I can’t seem to adjust how high the text bounding box is after I create one. I can only adjust the width. 2. Are you able to consistently reproduce it? If so what are the steps? I select the Type tool and drag out a box and I can control both height and width. After the box was created, I can only adjust the width. 3. Share a screenshot, recording, console log, link to the file, etc.

Hey! First of all, good job on the new API improvements. I am building something with variables and upon using figma.variables.createVariableAlias, I found inconsistent behavior between the editor interface and this method. Specifically, I am trying to assign variables to the InstanceNode (here, “Mode” prop key): properties["Mode"] = figma.variables.createVariableAlias(variable) This works, for string properties. For numeric properties, however, an error is thrown stating that the property that I am trying to assign can’t resolve to “string”. Now I assume this is because the API requires only string properties to be assigned (Working with Variables | Plugin API) - just an assumption - however this limitat

Hey, I’m running the current Beta and use some conditionals in my prototypes. For reasons I had to copy the whole prototype to another file. After copy the prototype the conditionals are missing. I used partly two or three conditionals in one action, I guess this is the tricky part. Would be nice to have a fix here. Regards

I have components with variants. When I click a component and then go back text doesn’t update. I selected “Reset component state” but it’s not helping 😦 HELP!!!

I have a design file that uses a library from another file. In this design file I’m using a component from the library — a button with rounded corners — which uses a variable number (30px) for the corner radius. When scaling this component in the design file, initially the corner radius variable is, as expected, being scaled accordingly. However, then it switches back to 30px. Clicking the corner radius back and forth made it go back to the scaled value, but then some components randomly switch back to the default value (see the screenshots).