Report a Problem

Hi! I’m working on a plugin to import a typographic scale, and according to the docs, and the api, the font weight seems to be missing as a configurable property. TextStyle | Plugin API I think this is a bug mainly because it’s part of what’s manually configurable as a textStyle, so it makes no sense to me for this single and very important property to be missing in the API. This is not small as it makes it impossible for my plugin to achieve its purpose functionality, forcing the user to make manual corrections on the imported typographic scale. Some similar plugins like TokenStudio seem to be over this bug somehow.

Since about 2 weeks autolayouts are randomly broken in various customer projects and only update themselves if they are touched individually with a mouse click… This is a massive problem when you are talking about design systems on enterprise level with tens of thousands of them! Our developers can’t work with something like that! Please fix it!

Hi there, Can anyone explain to me when the fontFamilyPostScriptName property is null and when it holds a value? I have added the API response to two different nodes, one with the fontFamilyPostScriptName and one without. "nodes": { "13:3": { "document": { "id": "13:3", "name": "desktop/headline", "type": "TEXT", "scrollBehavior": "SCROLLS", "blendMode": "PASS_THROUGH", "absoluteBoundingBox": { "x": 0, "y": 0, "width": 62, "height": 19 }, "absoluteRenderBounds": { "x": 1.1477272510528564, "y": 3.204545021057129, "width": 59.5511360168457, "height": 15.250000953674316 }, "constraints": { "vertical": "TOP", "horizontal": "LEFT" }, "fills": [ { "blendMode": "NORMAL", "type": "SOLID",

I am creating a simple dropdown that when an item is selected, it gets put on the top of the list in a variable called “ttselected”. I also want the dropdown to collapse after making a selection, but it does not let me do it. When I try creating the path, I notice that it sets it as “on drag” by default, and that “on click” is disabled" why?

figma crushes out right after I use any of the plugins that I used before this is very weird reinstalling figma, using figma beta, and reinstalling all plugins don’t help what the … I can’t work at all please help guys, this is a disaster

manifest.json { ... "api": "1.0.0", "main": "dist/code.js", "ui": "dist/ui.html", "editorType": [ "figma" ], "permissions": [ "currentuser" ], "networkAccess": { "allowedDomains": [...], "devAllowedDomains": [...] } } But error is thrown when calling figma.currentUser "in get_currentUser: "currentuser" permission not specified in manifest.json. Add the following to your manifest.json: "permissions": ["currentuser"]. See https://www.figma.com/plugin-docs/manifest/#permissions for more details." Figma typing version 1.78.0

Scrolling goes too much, too far and too… “wobbly” I’d say. M1 Mac, Monterey, didn’t update anything on my system since using prev. version Figma a month ago (which worked fine). The bug is present both in desktop app and in browser version.

Due to company policy, I can only log into my Figma using SSO, which is only accessible via Microsoft Edge browser. I haven’t been able to log in at all because the default browser that’s prompting the login is Safari and there seem to be no way to change it (I had already Edge as default browser) Current flow looks like this Click “Log in to Figma” Enter my email → automatically switch to SAML SSO Click “Log in” I get the error message saying “You can’t get there from here. You must use Microsoft Edge to access this resource” (see image attached) I click on “Launch in Edge” It redirects me to Figma app store page I click “Open” on the Figma app store page Back to step 1

New method figma.variables | Plugin API ignores spread value passed and always returns Effect.spread = 0

When copy/pasting properties from a component with variables to another component without any variables, the values that are pasted are only the variable values, not the variables themselves (see image).

I’ve built a component that has a couple different states (and more importantly, different sizes upon hover and click). I put that component within an auto layout frame and tested the prototype. The features resized correctly, adjusting the autolayout outer frame without issue. As soon as it became a component, the interactions of the nested component broke. I did find a solution, that each variant in the nested component needed to have the same dimensions. I’m wondering if anyone else has experienced this issue. It’s not quite a bug, and more an area of components that I don’t yet understand. Thanks!

After installing the latest release ( version 116.15.4) the Animate matching layers is not working properly. In the attached example I added an animate matching layers when switching from a frame to another and works well if there is no content within the different sub-frames, while it starts to bug when you add content inside. See the full video to understand what I mean. Before the update it was working properly, frames within frames with different names where switching and animating properly, while now there is a delay before the content appears.

This topic is entirely about Figma’s UI. It’s not about sticky scrolling behavior feature that you use when prototyping. The list of layers on the left side, when scrolled just right, can surface an annoying omission: clicking on a layer (on the canvas) doesn’t scroll to the highlighted layer (on the layers sidebar). This is because the parent frame’s item on the list is sticky and covers the highlighted layer. The application thinks the element is fully visible and doesn’t scroll - but it doesn’t know that the sticky element is overlaid on top. See the animation below. This happens very often to me when I’m jumping between layers to name them properly. Proposed solution:

Hi there, when I try to add a file to my favorites the tooltip text states that my limit of 20 favorites is reached. However, when I look at my left sidebar I just have 8 files inside my favorites list. I guess it is a bug? I’m not able to add my other 12 favorites.

Hi, I built the following autolayout: which should look like so: The outer autolayout has a fixed height and width. All the inner layers/autolayouts are set to width & height: fill. But here is what I actually get: And if I change the size of the outer autolayout it changes to something like that:

I created a prototype yesterday that had proper working animation. There is an icon that moves and transitions through various states after delays in each frame. Very simple, and yesterday when I stopped working it was fine. Woke up today and the animations are not working correctly. You can see in the attached video that its effectively doubling up the icon and doing some weird fading in and out. The names of the icon layers are the same They are within the same layer grouping I’ve named my screen frames ending with /## to keep things in order You can also see in the video if I remove surrounding content, the issue remains Like I said, worked completely fine yesterday, got up and overnight things dont work. Seems like Figma changed something? Anyone got any insight or help for this?

I am doing my animation and I want to check if my animation component set is working or not, So, I am doing press and hold to copy the component in the main frame. Still, while I was doing this, the hold and press were not working, I also searched for the shortcut key for that but I couldn’t see it anywhere. Please help me to resolve this problem I am facing.

Hi I am developing a plugin for Figma to convert whole design to website. As I was doing the final tests I noticed that when the reaction’s trigger is on mouse_enter, the trigger property of the reaction object is set to an empty object. You can check this by opening the console and create 2 rectangles with reaction set on mouse_enter and then type in console Figma.currentPage.selection[0].reactions[0].trigger and it shows empty object. Try to change it different trigger then every thing is ok. This bug is only happening on mouse_enter and mouse_leave Other triggers working as expected so I think it is a bug When I show(run) this in Figma it working correctly. if you know how Figma fetches this trigger, let me know please

Hello Community, The new update of fimga has messed up giving up CSS rules for shape (rectangle) having background blur. It just shows multiple color listing. @Figma_Support can you please look into this? Kind Regards, Divy

I’m having trouble setting a component that changes the state of its parent. I have done this flux: Create component A with default and hover variant Create component B with two variants (dropdown closed and open) Add component A as a child of component B. Add an On click → Change to interaction to the instance of component A. The two variants of component B will show up as options under the variant drop-down; you can open the drop-down, but you cannot select any variant besides the one that is already selected Is this a bug of Figma? Or is my fault?

When we assign a text style to a text frame, we lose access to the “details” tab. Therefore, if the text frame is not updated with the new text rendering method (update from last year if I remember correctly), assigning text style (that has this update accepted) doesn’t inherit the update. As we don’t have access to details after assigning the style we cannot accept the update otherwise than detaching style, updating, and reassigning style. Link to test playground: https://www.figma.com/file/NtqkUTg1cZXKHdusCtDMqk/Text-style-bug?type=design&node-id=0%3A1&mode=design&t=kuVM7xMPfCGzt57N-1

Hi, here is the example file: https://www.figma.com/file/AiYlhJZEIXMnLqZkF0rIj6/instance-bug?type=design&node-id=0%3A1&mode=design&t=EpBK27WgZu0y2aTv-1 Try to run prorotype flow 1 and flow 2 flow 1 is for instance of component and flow 2 is for detached instance First case - vertical transition/animation is croped And second case - it works properly.

Edit to: provide a more detailed error description and reclassify this as a possible API bug. I’m upgrading an existing plugin from React 17 to 18 and Webpack 4 to 5. I used the webpack-react sample plugin as source for the Webpack config file. Production builds are fine, but development builds break when it tries to bring up the UI. The issue remained when I backed off to React 17. I see this on the console: VM12806:4282 Uncaught SyntaxError: Unexpected end of input at onmessage (data:text/html;base64,PHNj … onmessage @ data:text/html;base64,PHNjcmlw … postMessage (async) innerIframeElement.onload @ Figma_app.min.js.br:1428 load (async) g4r @ Figma_app.min.js.br:1428 createInnerIframe @ Figma_app.min.js.br:1448 makeIframe @ Figma_app.min.js.br:1448 cb @ Figma_app.min.js.br:1522 (anonymous) @ Figma_app.min.js.br:1495 (anonymous) @ Figma_app.min.js.br:705 showUI @ VM12140:7

Hello, the context : in a page of a Figma file, I have a component with several variants in the same Figma file, I have another page which there’s a handoff section with ready for dev activated in the handoff section there are instances of all the variants of my component my problem : when I modify the variants of my component, then switch to Dev Mode, I go to my handoff section, and the compare changes are missing some instances that have all been modified indirectly by the modification of the variants. Am I only one to notice forgotten change notifications ?

Hello! I am developing an interactive plugin with asynchronous functions, and suddenly when I ran the development file I received a error I didn’t see before: ReferenceError: regeneratorRuntime is not defined. Here’s the full error code: ReferenceError: regeneratorRuntime is not defined at eval (eval at <anonymous> (eval at createScopedEvaluatorFactory (1d4564d8-5e8b-4125-a68a-5dfbedf1e353:1:1)), <anonymous>:3:20) at ./node_modules/@babel/runtime/regenerator/index.js (VM1251 PLUGIN_5_SOURCE:548:44) at __webpack_require__ (VM1251 PLUGIN_5_SOURCE:20:30) at ./src/plugin/controller.js (VM1251 PLUGIN_5_SOURCE:857:84) at __webpack_require__ (VM1251 PLUGIN_5_SOURCE:20:30) at eval (VM1251 PLUGIN_5_SOURCE:84:18) at Proxy.eval (VM1251 PLUGIN_5_SOURCE:87:10) at Object.eval (eval at createScopedEvaluatorFactory (1d4564d8-5e8b-4125-a68a-5dfbedf1e353:1:1), <anonymous>:8:16) at 1d4564d8-5e8b-412