Report a Problem

Me - “Oh Figma has another update, I hope they fix those long-standing bugs I deal with all the time. Especially the ones that have been lingering for a few years.” Figma - “Here’s some features that no one was really asking for. Oh, and we didn’t fix that 4 year old bug yet. But… you can now uh… AI integration!, no wait… stickers! uh, no wait, follow cursors!” Examples of what still hasn’t addressed properly: Linking between pages within a single document to make more efficient prototypes. In development terms, it’s similar to a separation of concerns. I’d like each page to represent a single portion of the application. Example, first page “home”, second page “documents”, etc. Prototypes in general. They are still buggy as hell. It’s sometimes easier to work with a developer to make a live working prototype than to manage them in Figma. Working inputs. I’d love to see inputs that allow you to type. You know, being that data collection in a UI (until AI takes over anyway) still r

I want to fins all the “WA” using Whole words filter and replace them by “WhatsApp”. By some reason it replaces the word not by “WhatsApp” but by “WHATSAPP”. There is no capitalized style applied. Looks like bug

If project having 10-15 child component and if you tried to edit or even try to do a minute position changes or hide/unhide layer to master component it freezes whole Figma screen as this changes are being saved real-time. ✔️ Actually it should worked like this: when user starts to edit master component a publish and discard changes button should appear at bottom of Figma screen, after editing complete when user clicks the publish changes button there should a progress bar appear that shows master component with name is being updating… This will not only help Figma users experience better but also help doing changes to component faster. Thanks Figma Team 🙂

Bugs Hello everyone! We have a problem, help as please:) Describe the bug Synced fields are being hidden, so they do not appear to be filled in All the users at my company face this issue. To Reproduce Steps to reproduce the behavior: See the screen recording Sync the file The sync goes through, but the synced text disappears We show that the text is hidden by toggling to the item and un-hiding it. (Can’t provide links to file + sheet) Expected behavior We expect the synced items to not be hidden. They should appear normally.

As far as I understand clientData on root component should be unique to a specific file. when I duplicate a file the clientData is duplicated as well, If I want to save specific file data It would start with wrong data and I will not know to identify this

Hi everyone! I have a bug when using custom cursor in Figma, They tend to change their size fir obscure reason, I linked two screenshots showing different size for the same cursor (only color change) Moreover, do a screenshot while using this feature trigger another bug (but not really important) the cursor in my screenshot have a different color and size than the one i was using, the screenshot with the orange cursor was blue and even smaller in reality The cursor in Figma is sometimes so small that it’s hard to use it, and i have to change to have a normal size cursor

As the title suggested, I use a UK keyboard and we don’t have the ‘§’ to hide or show UI. Previously, we used to use the tilde key to quickly show/hide UI However, this function has been removed in a recent update, can we please bring it back?

I received a link to a Figma file and I can’t star it. Or I can and it’s glitched. This is the view from the Recent Files page. It’s not clear whether or not this file is actually starred. Either it’s not possible for me to star this file or there’s a bug. Definitely something’s wrong though cause if it can’t be starred it shouldn’t be showing as “✔️ starred” in that dropdown. edit: There’s sooo little information available to me about this file that I’m thinking it came from outside our organization. Is that a thing? Would that prevent me from starring it? If so there should be some kinda messaging telling me I can’t star it and why.

Sometimes after creating components with variant interactions I can’t add typical interactions to cooperate them all … 😕

I see that other people in the forums have faced this issue, is there a solution, or what could be causing it?

This plugin API was working before, after today’s update we got this error Error: Unable to create style Any advice?

I keep having issues with trying to resize the layers panel. When I hover over the top of the panel to resize the height, it often doesn’t show the resize cursor / when I try to drag and resize, it just clicks on a layer. This is really irritating!

Whenever I enable the Dev Mode, the RelaunchData button are still shown under the “Plugin actions” section, but clicking them seems to be completely ignored. The plugin is not invoked and I don’t receive any callback. My plugin supports Figma and Dev modes + codegen. It also supports inspect, but I already tried it without the inspect capability and the problem persists. Is this a bug or some kind of incompatibility I’m not aware of? Extra info: Plugin is in still development (not published) I’m using Figma Desktop App (Optimized for Apple Silicon) v116.17.11

Hey team! Love your work with the plugin API! Just reporting the following issue: I batch import all the variables from my design system’s library on launch of my plugin using a combination of: 1. getAvailableLibraryVariableCollectionsAsync() 2. getVariablesInLibraryCollectionAsync() 3. importVariableByKeyAsync() I would love to use scopes to determine which variables can be applied where. Unfortunately, every variable’s .scope property returns the array ['ALL_SCOPES'] regardless of what the variable’s actual scopes are configured to. I know the scopes are configured correctly because the variables available in the Variable Picker UI inside of the editor are constrained as I would expect, but the plugin API is consistently just returning ALL_SCOPES. Let me know if I can provide any more info! Thanks!

Today, I received my invite to use Interactive components. But, i created a simple button with a left plus icon. And, on my interface I replaced plus icon to play icon, for example. When I hovering this button with play icon, it returns to original icon that is plus icon. Help us! 😃

All the buttons in this workspace frequently become unclickable, which can only be solved by restarting Figma. They will still fail after being used several times.

The scale tool doesn’t work properly on instances, (they are from another file)

Hello! Background: Created a branch for annotations from a ~200 screen main file so that UX could work simultaneously as design. The main file contains component screens and uses components from a large UI library. Issue: Main file screens had to be tweaked but the branch file did not implement the updates across the file. For example, one screen updated the copy but the same screen didn’t update elsewhere in the branch file. There are also minor formatting differences in the branch file (ex. the copy breaks to 4 lines versus 3 lines in the main file) as well as property booleans getting turned on within the branch file. Any idea on how to solve this? Thank you in advance!

Hey guys, If I have a component which contains other components and I want to have a WHILE HOVERING action on a child component, for some reason that’s not possible. It only works if the parent component is ungrouped so that it’s no loger a component. Is that a bug or a wanted behavior? Not sure I understand the logic behind it if it’s intentional. Thanks, Chris

In the design system of our asset library, an invisible component named “button-circe” was discovered, which, according to the asset search, refers to the master element in the “Draft Components” file. However, attempting to access its properties results in an error with the message “Unable to load. Something went wrong. Try closing this window and reselecting the component”. When I try to find this component in the “Draft Components” document, the search yields no results, indicating its absence from the system. This component represents an outdated version of another existing component and was removed from the system some time ago. Despite this, it still appears in the design layouts as a regular component without any error messages about deletion. However, attempting to navigate to its original component in the main file of the design system library does not lead to it, but into emptiness. What could be the reason? Is this some kind of bug?

The documentation states the following: Plugins in Dev Mode specifically built for code generation (“codegen”) appear in the Figma’s native language dropdown. Once selected from this menu, the figma.codegen.on("generate") callback will get called any time the user’s selection changes. This is working well for me the first time I select a language, no matter which one (I’m supporting 2 atm). However, whenever I switch to the other language, the callback is not called and Figma Dev UI shows a loading indicator indefinitely, but my plugin is never invoked. If I select another node or change the “select” preferences, then the plugin is reloaded and the figma.codegen.on("generate") callback is called with the new language. But again, if I try to select the other language, it goes back to the indefinite loading state. Notes: Plugin is in development (not published) No matter what language I select first, both work the first time, but the callback is not called when the other one is select

I’ve noticed that the user might unintentionally alter all the paragraphs in each paragraph just by using CMND+I on a parent element. Not sure if that’s intended, but to me, it’s a huge flaw knowing that reversing changes is quite destructive if you have deliberately overwritten the instance. This may eventually lead to very mundane manual work, which is why I’d recommend restraining switching font style of sub-elements when a parent (frame, section) is selected.

You can no longer copy css with a right click if box shadow has more than 3 values Box-Shadow Spread Values are discarded. Dev Mode is broken in that it turns box-shadow into css filter: drop-shadow This was working fine last week, but now it’s impossible to turn it into code correctly. Please investigate.

Our team is using local variables by adding colors with Opacity(alpha) applied. but on dev-mode, Figma don’t show Opacity(alpha) (ex. #ffffff 10% on local variables, only show #ffffff on dev-mode) Color on hexacode, local style can show Opacity in Dev mode, but Color on local variables didn’t show Opacity in Dev mode, We have already paid for the dev mode to use it, but it is a very critical issue. If anyone is experiencing the same problem or has solved it, please leave a comment.

Hello there I found a very pretty annoying and weird bug Figma rename randomly images while importing them By exemple by replacing “-” by “_” or adding numbers after it when there is not Before After