Experiencing issues? Report them.
Recently active
One of my most used keyboard shortcuts seemed to stopped working: Command + Right-click on an object to quickly select a child layer. After some troubleshooting I realized that this happens when “Right-click and Drag to Pan” setting is enabled. I like both of these features, and they should not be mutually exclusive. Can this be fixed?
figma bug what is this…?
I set the element width to fill in an automatic layout. When I change the direction of the auto layout, the element width becomes a fixed width. I have to set the width of the element again. I hope that switching the direction does not affect some of the settings of the original element, otherwise it will cause a series of extra work.
Reposting this as a bug since it isnt tagged as such, and years later it is not fixed: Link to nested frames Share an idea I asked the developer and there is a workaround. Instead of using the large blue share button top right, find the nested frame you want to link to in the layers panel. Then control-click, select Copy/paste as > Copy link. The link that gets generated then links to that specific frame. Hooray for Anders the developer!
I’m not sure if I don’t know how to use the ruler in the new Figma UI or if it’s a bug. I searched about it and tried a lot of ways and couldn’t get the ruler to work in the new Figma UI.
From what I’ve seen, this still seems to be an issue in UI3, as well.
Everytime i want to scroll to the bottom of the right sidebar (Which is floating in UI 3) i always end up scrolling the artboard instead of the sidebar / menu, as i have this habit of taking the cursor to the extreme right of the screen and then scrolling (Habit carried from the UI2), and everytime this happens, my flow state is broken and i have again carefully take the cursor inside the sidebar and then scroll. I understand the logic behind this change, but keeping the areas besides the floating sidebar interactive has no use, the only important section in the centre of the artboard.
Hi there, I would like to express my thoughts if this is a bug or not. I am using current version/release of Figma, and my organization is using Pro plan. I created a new collection, and this is the 20th collection in my UI Library. When checking in my project, there’s no indicator for updates from the Library, even if I tried checking it on actual implementation. Like to select what Action then select Collection. I badly need help for this asap. I hope someone here can help to discuss further the issue. Thanks you in advance!
Ok… here’s a strange one. After the last update (Current desktop Figma version 124.1.16) the color palette sticks to my mouse pointer when selecting a color from the library. It’s really annoying, see the video. I’m not holding my mouse buttons or whatever, it happens after the selection/click. When I’m clicking more at the bottom of the palette not in the middle. This bug happens when I did not scroll through my color palette It happens on my Apple MacBook M3 Pro Sonoma 14.1 and HP ProBook Windows 10 Enterprise. If this bug could be removed I would be a very happy fellow 😀 This bug really holding me back from doing my work properly.
With the latest release prototypes now have an option to set scaling “Responsive”. This is mega, but seems that overlays (elements/frames triggered via interactions) do not behave as responsive, yet? Like overlays are not aware they sit inside responsive viewport and they should adapt accordingly. Any hacks to overcome this?
I tried to share prototypes and a slide presentation with a client yesterday, and neither loaded for them in Chrome. It was stuck on the Figma loading bar. I was able to replicate the issue on my end as well. Brave works fine. Here are the versions client and then myself are on: Version 127.0.6533.100 (Official Build) (64-bit) Version 127.0.6533.120 (Official Build) (x86_64)
I would expect that this should be covered as a fix soon I have had to pick super short names for my variables to work around this but when using collections it becomes impossible. I find myself often disconnecting a component from variable only to ensure it’s linked to the correct one, which far from efficient.
For past 2 or 3 days, I’m expecting a weird bug inside Figma. I am unable to delete layers life, frame, shape or image, when they are inside any other frame. i happens when we update layer’s lock/unlock or visibility properties.
Once again this week I’ve ran into an issue concerning components/instances and variables. I was using a simple solid color gradient to mock a scroll fade, and when changing the color or layout of the gradient, all instances would update correctly as expected. But now since binding a local variable to the gradient (a local style) so that the fade gradient dynamically switches between light and dark variable modes, the instances do not update automatically, requiring me to find and click reset all changes on every instance. Moreover, even if an instance has been ‘reset’, if nested in another instance, the wrong variable mode is displayed. Only reason I started paying this last month for Figma was to refactor my files to be more dynamic with variables, yet it’s just constant headaches so far and my work has come to a halt. I’ve ran into more bugs in the last 2 weeks than I have with 3 years of daily use.
1. Describe the bug/issue you’re running into? FigJam allows the user to select items, right click and ‘copy as PNG’ When this is pasted in to another program or document on DESKTOP, the transparency areas are not honoured and turn black. Suggest that FigJam should output a PDF. 2. Are you able to consistently reproduce it? If so what are the steps? Select items, right click, copy as PNG Open desktop program (e.g. Outlook, Word, Illustrator, Photoshop, InDesign) Paste PNG 3. Share a screenshot, recording, console log, link to the file, etc. 4. Is the issue only happening in desktop app or a specific browser , or both? Happens when copying PNG from FigJam to desktop program. 5. What OS/version and/or browser/version are you using?
I’m back asking about something I don’t understand regarding shared libraries and the logic of the colour picker. Consider this use case: I have a Ui library shared called 💎 UI Token This library has 2 variable collections for colours Core Tokens → All Raw colours (not accessible outside of the library file) 🎨 UI Core → for UI elements, surface, border, icons, text… 🎨 UI Extended → Brand, hints and other non common use case Now I’ve named those collection in such way that when I choose a colour to assign in the picker, the 🎨 UI Core shows first in the list and 🎨 UI Extended second. Like in the screenshot of the Local Colour picker (within 💎 UI Token) For some reason when you open the same picker in another file the sorting order of the libraries is not the same anymore… 🎨 UI Extended is now first and 🎨 UI Core is second. I thought maybe sorting is reversed by mistake in shared library colour pickers. So I renamed th
1. Describe the bug/issue you’re running into? When I copy and paste a flow from FigJam into Figma, there is unexpected behavior whether flows show up or stay connected inside of Frames and Components. It seems the main issue is that connectors don’t stay connected inside of components, and FigJam flow elements don’t want to be placed inside of components. It also seems like Figma doesn’t know what to do with connectors that are not linked to a node on a Frame. My example shows many frames that have multiple connectors because of multiple touchpoints and paths on each screen. 2. Are you able to consistently reproduce it? If so what are the steps? Yes. Trying to bring flow into Figma Frame Copy flow from FigJam Paste into Figma on canvas. Try to drag into frame. SUCCESS! Either select all elements and create a Frame from selection, or select destination frame and then paste into selection. SUCCESS! Trying to bring flows into a Figma Component Copy flow from FigJam Paste into Figma on
Hi, we notice an issue inspecting icons in Dev mode. When we select an icon that contains a colour token, we can’t select the shape in dev Mode, and them we can’t see the token colour. Is there any way to see it? Thank you
Hi everyone The “select matching layers” not working after enabling new UI (recent Update) and then going back. Do any of you facing such an issue?
I’m using heavily variables in my prototypes and one thing that is beyond frustrating is when using Set Variable and I start type the name of the variable I want to setup, Figma is deciding for me which one I will be setting even if I’m still just typing. For example if I have 2 variables “transaction_info” and “transaction_1”, Figma If I type normal speed, by typing “tr” it automatically sets my variable as “transaction info” which is not the one I want to select. I would ideally prefer to be able to just type it all and not have to use this UI when coding logic and setting variables… but if I have to, could I at least choose what I want to set my variables to?..
I’m experiencing issues with exporting my icons. I’ve never encountered this problem before. When I export the icons as PNGs, they display correctly. However, when I export them as SVGs, they don’t appear as expected. Any advice on how to resolve this would be appreciated. png: ok: svg: not ok:
It’s more consistent than it was years ago, but still: so often I have to Restore default Thumbnail → Set as Thumbnail, then refresh my browser/app on the Files screen to see if it worked. Often it takes 3 to 4 tries for some files
Plugin API: REST API: The reactions data is missing. However, it was normal a few months ago.
I’m using this amazing hack to keep images’ aspect ratio. After the last update, each time I wrap such an image in auto layout, it looks like it affects the internal auto-layout settings.
When I try to only apply the Hugh Content to the width, Figma applies it to the width and height, but I only want to apply it to the width. Does anyone know how I can make it only apply to the width?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.