Report a Problem

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

Hello Figma, I’ve encountered an issue when using typographic variables. I’ve configured all the fonts according to the parameters allowed by the program, but when applying them and switching to prototype mode, it doesn’t respect the settings established as variables. In my case, I’ve used two different types of typography, “Flexo” and “Nunito,” but both font families have different names for their weights. My question is, does this affect the variables? I’m attaching a video of the issue I’m facing, and I hope to find a possible solution to this problem.

hey guys, im a new member of Figma’s community just as user too. Im facing an issue about editing texts on instances, the changes just dont appear at all, however, the changes remains as the master component. in design mode everythings okay, but it dont appears in a presentation view. Can someone help me plss? thnks for all

I have a dropdown instance. In its open state I changed the text. But when I tried the prototype preview mode the text and the component keeps changing to the default text from the main component. Can you guys help me? Go to file

We are using variables for our enterprise components (things like color, border radius, etc) the typical token items. We are working to integrate them into illustration, logo, and pattern component libraries. So that these items swap out depending on the brand (mode) picked. It seems to work, but when Figma reloads some of the visual items or full components will “disappear” (they are there but broken). This is not the same as the bug where you can click into the disappeared element and it reappears. Everything fixes itself when you “CMD+/” and “Re-Resolve Variable References”, but to visually see the changes of many of the items we have to re-resolve every time Figma reloads. This is a big issue because we need developers and stakeholders to be able to use these designs and see the correct variable of the components. Is there a way to make it where the files “Re-Resolve Variable References” automatically on load so this isn’t an issue?

Hello, I’ve been working on this prototype for a website and just finished a carousel menu that will nest within a section of the landing page. I’m trying to figure out how to nest this carousel within a frame that can then rest on my landing page, while preserving the interactions I’ve already created. However, every time I place my carousel within an empty frame and activate “Clip Content”, it somehow makes my carousel interactions completely inaccessible in Prototype Mode. I’ve tried playing around with the ordering of each of my items, I’ve searched YouTube and the community, and nobody seems to have this same issue. I can’t figure out what the heck I’m doing wrong and I’m losing my mind. Nesting a carousel in a frame shouldn’t do this, should it? Here are links to my prototype and the workstation so hopefully you know what I mean. If you need more info please let me know. Figma – 19 Aug 23 https://www.figma.com/design/A4ohfKnTR17g3YjEsOcsRe/Responsive-DIY-Website?node-id=145-82&a

Situation: Component File (published as a library) Screens File (using instances from the component file, combining them into a page design, and then also used as components library for the next file) Feature Presentation File (using the screen components from the Screens File to present new feature requests and updates to product team) Component File → Screens File → Presentation File Problem: Normally, there is no problem and everything works fine. However, sometimes Figma successfully uses components from the “Components file” in the “Screens file”, but fails to show the exact same component in the “Presentation file”. Sometimes even shows weird stuff instead. (See screenshots) I tried: closing & restarting Figma changing something so I can publish a change hoping that it will affect the other files. It would be nice if this bug would be resolved. 😉

Suddenly today I noticed that my prototypes started freezing. After some investigation I found that by removing the “Mouse Enter” variant change that I used for the hover effect on my buttons, the prototypes started working correctly again. I’m not sure if this was the cause but it did resolve the issue. (note these had been previously working) Image below to show how I had the buttons setup using the “Mouse Enter” and Mouse Leave" triggers to switch between the two variants.