Report a Problem

Bug: when moving on the canvas (middle mouse button) starting with the cursor above the link. The object is moved instead of moving the viewport on the canvas. I think it’s a bug, because it’s a very strange and unexpected action While I was writing I found a second bug, when you move the viewport over the canvas (by pressing the middle mouse button) and if you are editing text at that moment, then when you start moving over another text, you will not move the viewport over the canvas, but will start editing the text. It seems that the program incorrectly handles the middle mouse button over different objects and takes it as the right mouse button.

To zoom I like to hold z and just drag a square around where I want to go, rather than clicking a bunch of times. But it when I do this, it lands me too far to the right. There’s some calculation that’s off, and it doesn’t seem to happen in other programs. Anyone else have this issue? It’s only with the app. The web version seems to work fine.

Hello! Recently, I change master icon color and the instance doesn’t change to master color. In the past this worked fine, all the child layer of icon named Vector for consistency. Here’s the file you can check out. Thanks Figma test - Instance not change color.fig (108.7 KB)

Hello there, We encounter an issues while searching for any plugins or any widgets, we have these error messages : “An error occured while searching for widgets/plugins”. Here is the one for the plugins (it’s same format for the widgets) : Do you please have any clues on that ? Thank you

I was trying to export all VectorNode properties via ExportSettingsREST, but vectorNetwork or vectorPaths are missing - it’s impossible to reproduce vector node in my app.

As the plugin API document says, the group api allows to create the new group while keeping all the grouped layers in the same absolute x/y locations. However, it dosen’t work as expected in my case: // the absoluteNode has the layoutPositioning "ABSOLUTE" figma.group([absoluteNode], absoluteNode.parent); // the x/y locations of absoluteNode are changed, and the new group has the layoutPositioning "AUTO" Also, I’ve double checked the “Group selection” menu in Figma editor and it works all right. It seems that there is bug in group API. Hope it to be fixed.

While working with the createVideoAsync and fetch we have notice recently the both functions have become slower to the point Figma crashes (the file) because it ran out of memory trying to load the video though the plugin and it started to happen in the last couple of months. Video Files that are less than 50 mb mostly work but are taking longer than normal to fetch load. Loading images works fine. And loading the same videos manually by dragging them into Figma works fine too. The code we use to load that is base on the documentation const component = figma.createComponent() const response = await fetch(url); const buffer = await response.arrayBuffer(); return figma .createVideoAsync(videoData) .then(async (video: Video) => { component.fills = [ { type: 'VIDEO', videoHash: video.hash, scaleMode: 'FILL' }, ]; }) .catch((error) => { console.warn(error); });

We are using Figma to create template components of what we consider Universal experiences. I am trying to utilize instance swap for Headers and Footers. It works great, but there is a bug where in the template (component) document the breakpoint variables break. So they always show as a single version (Desktop/Tablet/Mobile). But when I copy the component into a different file or full it in through assets it is working as expected and the swap works as expected too, basically it unbreaks itself. It has been hard to create the template components with the correct options when not visually being able to see that it is working. Any help would be appreciated. Thanks! -Amber

Toggle buttons like “Constraint proportions” or the visibility eyeball seem to retain focus, even after hitting the Escape key. Users have to click somewhere to remove focus. This can be irritating if you click one of these buttons (or accidentally tab to one of them) and then try to use arrow keys to move the selected layer, or the Delete key to delete the layer, or the backslash “/” key to select a parent layer – all of which will do nothing until you use your mouse/touchpad to click on the layer again (even though it’s already selected).

A file ownership was transferred to me. As a new owner, I can’t move it to a private team/project folder so that I can manage the invited accounts on it. The file currently only appears in my ‘Recents’ tab.

After your updating with resposible windows it always have to reload, and i always have to change window size to to place it under an open frame, since it no longer opens automatically to fit the frame size

Trying to share my file, toggle is off (restrict copying), but anyone with the link still can copy and paste every frame from my file, they just can’t dublicate the whole file. Is it a bug or something? My file: https://www.figma.com/design/wMAskUOvYZ4Ensh89chd6g/Untitled?node-id=1-948&t=d5XYNuq5EnB0CZFI-1 My settings screenshot: Imgur: The magic of the Internet

Hello, i can’t access the shortcut to switch from slide to grid view. Using an Azerty k/b and the “.” is only accessible through shift. (if i change to generic k/b then it works). the @ shortcut to view/hide interface as well. Which is strange, since the multiplayer cursors seems to work (cmd + alt + @)

The title says it all. I should be able to perform the same actions regardless of layer visibility. This also shows the crazy amount of lag variants can have.

When you move an action from one conditional to another, and there are unassigned actions in any other conditionals, the system duplicates the moved action to any other conditionals with unassigned actions.

The title states it all. I know the mods keep merging these posts into one, but this issue seriously needs to be addressed. It’s a productivity killer.

Hi, we’ve been facing a problem on our Design Systems. The shadow values keep detaching. First, after introducing shadow variables + shadow styles, we thought that the problem was the newly released shadow variables. However, even changing back to using raw numbers, the shadows kept changing back to a default random value for every single property. It’s really messing up our workflow. Do you know if anyone already reported that? Thanks Rodrigo

When you have a boolean variant property (i.e. variant with true/false values), click the nut icon to assign a variable for it, and click + to create a new variable, the popup will create a string variable and you can’t change that to boolean. The popup should default to creating a boolean variable for a boolean property. To assign a boolean variable you have to first create a boolean variable and then assign that.

Suppose we are using Figma variables for a calculator screen. You do all the operations and it’s a functional calculator. Though, when press “8 / 0” (eight divided by 0), Figma crashes (attached image). As in the math, and programming, this should be properly handled. The solution can be a toast message in Figma, saying “can’t divide by 0” or do nothing at all.

When I create a slideshow with frames it goes to left and right thanks to smart animate. But interactive component ignores the second drag interaction. Demo

To recreate my issue, draw a frame, then a rectangle inside the frame. Then, with the rectangle selected, click the ‘Align Top’ button (or any align button). Then press an arrow on the keyboard – nothing happens because the focus is still on the alignment button you just clicked. This has only started happening recently but it’s pretty annoying and slows you down a lot when you’re a lightning-fast POWER USER like this hombre.

There is one thing that me and my teammates are really mad about😅As you see here the masking is not working well for files with thumbnails.

Hey ! We have built Blocks plugin to simplify wireframing. https://www.figma.com/community/plugin/1332372435133832847/blocks It works as a kind of droppable Components from a Library. We are facing regular Search problems with searching within Components for variations of icons. Concrete examples : typing a keyword that matches an icon yet no results found typing the same word yet receiving 2 different list of resutls Do you face similar feedbacks ? Or is it related to our Component Architectures where a component is dropped (copied) from a Library in another Figma file, and that the component you drop nests other component from this other file ? Many thanks in advance for the insights Best, Vic i

There’s a weird bug where if you select all these frames and apply auto layout, yes it applies auto layout individually to each frame. Except, if you press auto layout, it renames all the items into the same name, causing a conflict in variants, which is really annoying. As a result, you have to press auto layout one by one for it to work.

Hi all, simple question to Figma for all of us → Any changes to stroke properties = having to close your prototype tab and restart. For some reason, any changes to a stroke, will not propagate to the prototype in real time. Nearly all changes almost kinda magically, and awesomely get reflected instantly on an open prototype. But strokes? They aint playing. Genuinely curious why this is the case, from a technical standpoint ya know? And stroked elements in UI are pretty ubiquitous, so it effects the work-flow for Figma users a lot, for me, daily, often several times a day. Just asking out loud… what’s up with that? Can we expect a fix anytime soon? And why is it so hard? I’d imagine Figma would be aware of this and would have fixed it ages ago if it wasn’t hard. Cheers, Marc