Report a Problem

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. It would be nice to show on the color palette what colors are hidden (at least). But the best option would be change all the corresponding colors at once.

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 button and min-width on the text-only button. I expect these overrides to apply at all times to all variants of the subcomponent. If I use the button component as is, everything seems to be working fine and property inheritance and overrides are working. It is when I start using the button component within other component

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. The issue comes when I do a smart animate transition between two copies of this frame at different heights. In this case, the individual constraints of the circle get ignored and the two states of the entire object are stretched and crossfaded. Is there anything I can do on my end to address this or is this a bug that can be fixed? I had high hopes when the manual resize worked.

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 handler does not log any message, despite a document change occurring. This behavior is inconsistent with how the DocumentChange event should work. Any c

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. 4. Is the issue only happening in desktop app or a specific browser , or both? both 5. What OS/version and/or browser/version are you using? Google Chrome Version 90.0.4430.9

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 limitation doesn’t exist when using the editor: In editor, numeric variable can be bound just fine. This is quite a big limitation, because any real conditionals will usually work with numbers. Possibly I am missing something, but this seems like a bug in the SDK layer to me. Thank you!

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).

Hello everyone, looks like after recent Figma API update (August 31, 2023), my plugin stopped working properly. At least that’s my assumption because it worked yesterday without any problem. But based on what I see in the changelog, there are no updates to what is used in the plugin. The issue is that Figma plugin API do not support Reaction.actions as array, only Reaction.action (Reaction | Plugin API), but in development my plugin is now throwing an error: This node contains an action in its Reactions. Please update the actions field instead of the legacy action field in order to prevent potential data loss. Any idea what the problem might be?

we have used variables to style an object in figma (e.g. colors as fill, or numbers as auto layout and radius properties). when copying properties using ctrl+alt+c, its expected to style new object with variables, not static values. but figma uses detached variable values to style new object. This behaves right when using styles, but variables cannot be copied correctly. so its annoying to set each value manually.

Hi there, I’m trying to get xaml code for my Figma design, and always get this error. What can I do?

I feel like variables are such a powerful tool but it’s just not usable yet. I’m having this very simple issue but it’s breaking the experience for me. I’m creating a list of buttons and each button sets lots of variables all at once, but, whenever I copy this buttons and paste into another frame the prototype actions that I set up simply break: I copies all the “Set variable” actions but without the actual variable, so I have to go on each button and rewire every variable which is a pain.

Hey everyone, I’m currently working on a Figma plugin that involves Styles, and I’ve come across an unexpected behavior with the DocumentChangeEvent: I noticed that when a user opens the “+” pop-up in Local Styles to create a new style, clicking on any style type triggers the DocumentChangeEvent with all three possible style changes (create, delete, property change) at once. However, at this point, nothing is actually created, deleted, or modified, so the user is notified about changes that didn’t happen. Is there a way to work around it? I want to avoid notifying users about changes that haven’t taken place yet. Thanks in advance.