Share Your Thoughts

It would be great if the shape tool did not add a fill by default. This allows for quick wireframing and makes it really fast to use InVision Freehand for whiteboard jam sessions. With Fig Jam, I need to choose to hide the fill every time, and so do all the collaborators.

It needs to be easier to zero in on the specific things that were change in a branch review. For example, I have a branch where I add a simple line of copy to one frame. But when I review that before merging, it shows me an entire section without multiple layout frames in it. One of them has the new text line, but how am I supposed to know that? See the screenshot below - I made the additional text bigger so you might be able to spot the difference. But what if it was the same size as the rest of the body text? It would be better if it highlighted the specific difference and allowed you to zoom in/out at the parent/child layer level. Dev-mode has a feature that is a little like what I’m talking about. It’s the “Compare changes” that have been made after marking something as “Ready for dev” feature. Even though this doesn’t always work that well either, this would be more helpful than what is available now for reviewing branches. Dev mode change review

I’m crying to see the “color theory” in Figma – as in Color Wheel - Color Palette Generator | Figma All the classic color theory, the accents, opposite or adjacent color, it’s built on the classic artistic color wheel, which is RYB, not RGB. This means the opposite color pairs are red-green, orange-blue and yellow-purple/violet — not red-cyan, yellow-blue and green-purple as on the RGB wheel. If you apply the RYB algorithms to the RGB, the results are wrong, unpleasant, disturbing. See the “correct” color combinations on the RYB wheel, check the opposite and adjacent colors work together much better in my tool Paletino BETA (v1.09b) – it’s not finished yet, some things (like exports) do not work, but the core does work fine. I’ve been insterested in this topic for 25 years and I created a couple of color mixing applications and tools and I really believe the Figma approach and using classic color theory with the RGB is wrong. Big mistake producing worse color combinations.

We do a lot of synthesis in FigJam for customer support tickets and feature requests. It’s really tedious to bring all the data into FigJam though because I can’t import a CSV or bulk copy / paste issues titles. Would save me so much time!

Need search with name or describe，and Easier unloading

Omg, I just came to realise that presenting a realistic scrilling website prototype for a client or developer is so much extra work. Right now you need to reset the height of the frame then set clipping (because this is just not how you are working while designing). Please Figma Team add viewport height and scroll option like in XD to make this a lot easier for huge UI prototypes with a lot of content and going back and forth right now… I can’t understand how isn’t this a highly voted request. No other ex-XD users in Figma Community? 😃

Hello, I’m frequently using the Plus Lighter and Plus Darker blending modes, and I’ve encountered an issue with adaptive fills. I have a Translucent Fill variable defined as (#FFFFFF - 50% [Light Mode]) and (#000000 - 50% [Dark Mode]). Currently, there’s no way to switch between Plus Lighter and Plus Darker blending modes based on Light or Dark Mode. Is there any plan to support Blending Mode Variables that adapt to different themes? Thank you!

As you announced the Design Panel on UI3 can adjust its width. I did hope that it will resolve my problem: more space to display loooooong variable names, but no. Though it is good to be rearranged but I also want it to be adjustable.

One of my clients is going through a rebranding process. I need to reroute many color variables at once, replacing a group of color variables with another one. There is no easy way to do it, and none of the plug-ins that allow swapping variables will swap variable groups, only collections. I have to go into the Variables panel and change one by one, manually. If Figma had an intelligent find and replace system for variables, where I could, for example, replace all color/component/primary tokens with color/component/secondary tokens in batch, that would make my life a lot easier. It would be especially great if it worked similar to text find and replace, where I could define if the variable name contains or does not contain, matches or does not match a string or a collection name or a group name, and similar kind of rules that allow for advanced manipulation, that would be amazing.

Most of the time when I’m interacting with a layer that is not inside an auto-layout, Constraints is what I care about the most since it gives me more control over the relative position of it when resizing. Please bring it back out. It’s frustrating having to click a small little icon everytime just to open up the Constraints panel

TImes I have been working in a file and want the assets panel to show: 0 Times I have been frustrated that the assets panel is showing by default as it is a library but I want to access the layers panel: 1,923,328 OK OK, that is an exaggeration, but since I find the Assets panel confusing, poorly designed and not very useful, I never use it. I am always either copy/pasting components, or using things like ‘insert’. I NEVER want to see the Assets panel and I am constantly being annoyed I have to manually switch to the assets panel, many times a day. I find it weird it defaults to that as well, cos when I am in a library I am working on the assets, not needing to pull them into the canvas. I also turn all my files that consume design system libraries into libraries themselves, cos I often make entire artboards into components so they can be duplicated elsewhere in the file and automatically update with changes to them, or place them into other files.

I think that’s the new feature “nested components” need to be more functional. For example: I have a card with nested component button. But the only parameter that i need to edit is icon on this button, all other settings useless in this component. I thinks it will be cool if i can disable some of nested component’s paramters like show icon or btn size and leave only icon-type parameter. And it will be more cool if i can make preferred icons for nested component (in this card i can choose between filled like or unfilled)

I want to suggest that Figma should allow users an avenue to remove their data from AI training retroactively if the toggle was switched on in error. We know users make mistakes and not allowing data deletion requests gives very little room for error.

Hi there, I’ve been running into this issue for a long time now, which is why I’m making a separate topic for it. We have multiple themes that have multiple groups of colors which make the variable names of colors quite long. The consequence of this is that you cannot see the full variable name in the “Selection colors” panel in the bottom right corner. The panel cannot be enlarged and there is also no tooltip to show you the colour name when hovering over the color. In other places there actually IS a tooltip when you hover over colors, so it’s kinda strange that there is no such feature in this specific section (where we need it the most in our project). So can you please add this feature to help us solve this issue? Next to helping us, it would also make the interface a tad more consistent on the topic of tooltip usage… Thank you in advance!

I feel like Im moving at a snails pace. I type out primary I tab to the next column and hit enter… nothing happens. I tap spacebar or something to bring up the color picker. Nothing… I move to my mouse and click on the color swatch… No I don’t want to define a custom color, I need to click on Libraries! Stop this madness, let me start typing for a named color already! I click on libraries and what do you know… I have to click AGAIN on the search bar. I now move back to typing on the keyboard I hit enter and yay! I now defined one of the variables. I tab over and… wait, where is the focus? Idk focus is gone now, I can’t tab over to the next column. So I move my hand back to the mouse to double click into the text area, and move my hand back to start typing to find my named color. Wait, this doesn’t do anything!! I have to go back to the mouse and click on the tiny swatch, click on library, click on search, search for my color. Stop forcing me to do this silly dance for all my 100 co

Good morning, I hope you are feeling very well. Regarding the sharing option, because Figma automatically takes it as an extra entry and charges it to the bill, in the professional plan it appears that you can share files. I think the best thing would be if they automatically placed the viewr restriction option and if you want to change it to the edit or view option, notify that same day that there will be an extra charge. I look forward to your response and have a great day.

I have multiple Figma accounts with multiple clients and multiple projects. I also have a handful of designers on my team. Because all of us manage changes requested by the client, we often miss some tagged comments because the structure of notifications in Figma is just a long list. I would love to be able to tag comments as “To do list” and then reference and jump to all those action items and mark as complete. The more I convince companies to adopt Figma, the more comments there are (by non designers). I’d also love to tag comments as “ideas” or by topic so i dont have to guess click on everything to see which comments i need to look at. Essentially I want to “View groups” of comments that are most relevant and just hide the ones that are needed on the page for others but are in my way when I’m doing my work.

I have some specific naming values for SVGs that I make with Figma, sometimes names of the frames become too long that it doesn’t fit in the stroke, but doesn’t fit even while I am hovering over the name. Can you make it like 6 row high or anything else?

Continuing the discussion from Overlay full widht: I’m currently designing popups for our mobile app and faced a challenge. I want the overlays to automatically display at full width in the prototype, without having to manually adjust the size every time. As noted in the community, Figma currently doesn’t support this feature, and we have to manually match the overlay width with the previous frame. I hope Figma considers adding this feature, as it would greatly benefit all users, especially those designing mobile interfaces or working with popups. An automatic full-width display for overlays would simplify the process and enhance design consistency. I encourage the Figma team to take this into account, and I welcome thoughts and suggestions from the community. Let’s hope this feature becomes a reality soon!

I noticed that when typing text in the Figma interface, the result of pressing the escape key is really inconsistent. It’s causing me to lose a bunch of changes that I painstakingly typed out, just due to muscle memory. For example: Typing normal text object: Esc to submit Renaming a layer: Esc to cancel Renaming a page: Esc to cancel Renaming a property: Esc to submit I always avoid hitting the enter key because in most apps and use cases, the enter key creates a new line. So I always reach for the escape key – and then my changes get thrown away when I don’t expect it. This is really bad if I’m individually renaming many layers in succession and forget to check. It would be great if Figma could just pick a behavior and stick to it so I don’t have to keep consciously remembering which key to use for the SAME action.

After month of no activity any idea in forum is closed with “this topic was automatically closed 30 days after the last reply. New replies are no longer allowed.” But the locked discussion still has votes. There may be 5 replies with 50 votes. Than someone creates a new post on same issue, usually without reference to previous one. And issue receives votes there. Which makes it appear to have lower number of votes because they are now split to 2-3 topics about the same issue. Figma could easily disable closing after 30 days, but this remains enabled. Or moderators could merge topics and votes, but they don’t. Anyway, what’s the point? This is a graveyard of ideas anyway, hardly anything ever getting implemented.

I’m not able to select layers that are visible, but don’t have a fill applied to them. This seems like bug level to me, and I noticed a couple of threads that bring the issue up but have been closed without any updates. This really hinders me in trying to create quick prototypes where I’m working off Sketches or screenshots and don’t have the time to fully recreate a design. I’ll usually draw invisible boxes to use as click areas. Unfortunately if I do this I can’t select any of them directly, and instead have to hunt for them in the layers panel. Please fix this! It shouldn’t be the same thing as hiding a layer!

I’ll share some ideas that i had and think that would be helpful on FigmaJam Guide ruler: this ruler would be able to use horizontally or vertically (90º or 180º) and only the person who added the ruler could see it on the page. It would help to organize and keep things aligned, even if the object (shape, sticky note, text, etc.) is in diferent sections. More objects can be rotated. I like using post-its, widgets, washi tape and other things, but it’s annoying not being able to rotate them… Because not leaving all the objects at 90º keeps, in my point of view, the page more visually pleasing

@Manuel_Barrio said it here: Fix naming when creating component variants The behaviour of adding Variants to components should not change depending on whether the component name is simple or compound (using slashes). The component naming using slashes should not be used to determine the name and quantity of variants created when using Property > Create Variant. Adding a Variant to a component should always just add 1 new Variant and leave the component name as the user intended it. It is a much more common use case to add variants to a component already in use than to create a bunch of variants based on a component’s naming structure. Workaround: cut the component name and replace with a letter, then create the Variant, name the variant property and then paste the original component name back. As Marco says: “boring”.