Report a Problem

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

Hello! I came across this visual bug while just zooming in and out. It’s only present under these two frames and it makes no difference, if I try zooming by mouse or trackpad. It’s not a breaking bug by any means, but I wanted to share it nevertheless :)) Have a nice day <3 Update: It’s fixed by moving the frames once 👍

You need to do something with it, because the way drag direction works when you made 2 drag triggers is not clear, i want to choose what have to be when i drag in left or right direction, now i can made few drag triggers but cant choose the direction and it sets automatically, and not always the way it has to be. Make something with it please

My colour picker keeps closing after clicking inside of the HSL colour area once (not number values). Sometimes it does work and allows me to click around and keep adjusting the colour but 80% of the time it just picks the colour and closes. Has been doing this for a couple of days. Tried using my trackpad and another mouse but the problem persists. Using the desktop app and an M2 Mac Air if it helps.

I have gradients of the exact same settings (color and angle) from 2 different files. I was trying to apply what I experimented into my design system file, only to find that they look different even though the angle adjusted is the same. Even the CSS is dev mode for the angles are different. Sample file link

Hi, we have an issue with a prototype and the password function. When sharing the link to others, the “testers” of the prototype copy & paste the password into the password field and they receive the feedback, “password incorrect”. If you copy & paste the password a second or third time, the password will work.

I don’t know if this is only happening on my end. I have tested on multiple browsers. When viewing a file in the Figma community, I try switching pages in the preview embed box and it doesn’t seem to work. is this just on my end or an actual bug? Its hard to preview files before downloading. #community

Now if the layer has a blur background effect, backgrounds that shouldn’t be present when exporting will also be exported (layers not in the target Frame) This behavior is different than before, and it breaks many old designs.

Hi everyone, has anyone ever experienced this? We’re on a project that required a few different libraries and typestyles sets attached to one working file. We’ve done a lot of work but recently we’ve noticed that on designs we have wrapped up months ago, at random some type fields would be reassigned from one library to another. There’s no pattern to it, some random fields on random art boards just changed from the original style we applied to one from the other library. Anyway, if anyone has any experience with this, we would love your insight! Thanks again, and have a great day. 🙏

Screen record: Dropbox Capture Figma file: https://www.figma.com/design/Fz4GPUPcObdBBO2iATQI3z/Untitled?node-id=0-1&t=wgWbjK7tqTZG9rX4-1

While working on a FigJam file with another editor, suddenly, all the connectors created between text boxes disappeared. We were working on the Figma app for Windows 10 desktops.

Hi there, when running a prototype on iOS the status bar is visible at first. After the two-finger long press the bottom sheet slides in and the status bar disappears. Returning to the prototype displays the frame without the status bar. After second two-finger long press the status bar appears again. Returning to the prototype displays the frame with the status bar. Screenshots were taken on an iPhone 13 Pro Max Would be nice to let the user decide wether to hide or show the status bar in general. Best regards Michael