Suggest a Feature

the new autolayout behavior I’ve had for the past few weeks (automatically setting child elements to fill with new autolayout set to fixed) is painful. I wish my settings could go back to when wrapping an element with an autolayout didn’t change the element’s behavior properties and the new autolayout was set to hug

I recently started working in more detail with Figma’s Variable and Prototyping tools and have noticed a few areas that would help make my life a bit easier. There are a number of them that I discovered have already been mentioned on the forums so I’ll skip those. The main one for this topic is as follows: I have a somewhat detailed organisational structure for my variables and given that the panel sizes for prototyping are so small it means I have to rely on the tooltips to know which variables I’m looking at sometimes especially with variables with the same name (since I use groups to organise them). The problem here is that not all variable fields in the prototyping popups or panels have tooltips referencing the path to the variable. Which means I have to often delete and re-add a variable to make sure its the right one. Until such a time as we have an improved UI for prototyping, it would be great to have the tooltips work universally.

It is impossible to write in Georgian

It is very annoying to create font style for your UI and then have to break them due to various options not offered. The only options available when you have created a font style are List Style and Truncate text (please add middle truncation too). When you break the font style you get all the other options. I need to add Underline, Case, and Strikethrough to my font style but it is not available.

I’m working with a design system that is increasing in size. Because of this, it would be nice to have control over the property window modal size. I find that I’m always scrolling to find the right color or style. Also - I use a Wacom tablet which is notorious for scroll bugs, so this added scrolling is a small challenge. Any others feel like this would be a good feature request?

Request a feature in Figma that enables switching between flows directly in preview mode. This will save time by eliminating the need to manually select different flow screens.

unless I missed something, it looks like I can only link text and can’t link a button I clopied in from our design system

I really found out Figma slide is very interesting, and I know it’s in a beta version though here is my thoughts and suggestion perhaps 🙂 • when shifting in design mode using shortcut key(shift-D) it doesn’t show the layout grid tools/panel, but when you click it in the tool bar it will show, I think it’s a bug. • Can we just remove the remove the round corner in slide itself, if doesn’t hide the overlapping elements or outside elements, or maybe had an option similar to regular Figma mockup design had a option to toggle hide outside elements 🙂 • Create and able to create a custom brand templates instead of relying on pre-template made? • able to connect or use the created design system from regular Figma design. • Animation stuff unlike to powerpoint it’s more reliable to use powerpoint because capabilities of having lot of animation options. • morph animation or smart animate, bind text properties to animate to next slide, specifically like letter spacing, font size,

I’m loving slides so far! But the lack of configurability in exports is a bit of a challenge for any serious usage. I noticed that most of the text isn’t text selectable in our PDF’s, there’s no image compression options etc.

Is there a key to hold so you drag the frame? If I have three graphics in three different frames, and they are all in an outer frame, is there a key I can press (or combination) that would allow me to quickly grab just the outer frame and not just an inner frame by itself? And if there isn’t, can there be? lol Too many times do I accidentally grab the contents of a frame or an internal adjustment feature, instead of the frame I am trying to move. Thanks!

I appreciate the idea behind the menu updates in UI3, but it seems like the team made some decisions about what should be shown at the top level that users here are regretting. It would be nice to have an “expand” option on each section of the right menu, that lets you by default see all of the properties/tools available for that section, without going into the overflow menu. Here’s a mock-up:

Let me explain what I mean. I found and bought very useful Figma templates and libraries from the Community section. The problem is when I want to use such a template I need to make a copy of it that is then stored in my account (e.g. “Version 1.0”). If the original creator then releases an update of this library or template (“Version 1.1”) its a manual overhead every time to replace the file and relink my components. Is there no smarter way to get such files automatically update when the original source gets updated? Or is there a better way to go about it? That’s one of the features I miss from Sketch libraries. Thanks!

This language massively used for ruzzian propaganda, they are invading because everyone must use this language or because not used as government-level language. Ruzzians in other countries wants to use not local language(or english), but their and force them to speak in a language they understand(ruzzian), livin in European countries hating Europe/West and loving Ruzzian and their genocide against Ukraine. Also will be so good to disable access to Figma for ruzzian costumers

I would like to lock group access so I can not select inside. Only up to that group. What will help me a lot when I moving groups around. I could just use CTRL + Click and quickly select group with all the elements we need.

the fact that someone is forced to create an account just to open a slide presentation I want to share is criminal and unethical. This alone is a reason to not use this product the fact that by clicking anywhere on the slide take me to the next one should be optional and/or there should be the option to deactivate it so I can have better control on the navigation. It’s easy to move to the next slide by mistake but is not as easy to go back

It would be nice to be able to choose the slide to animate to in Figma Slides. Currently animations only apply to the next slide, but if we could choose the slide it would allow us to create looping animations. Example: In my latest slide deck, slides 1-4 were created to show an animation on the title slide. I’d like to smart animate from slide 4 back to slide 1 so the animation automatically loops while the title slide is being presented.

I use sections a lot to organize artboards and I set these sections to Ready for Dev when work on these artboards is done. When I move these sections around the canvas (to organise the sections themselves) I have to update the Ready for Dev. I tidied up and now I have almost 30 sections that need Ready for Dev updating.

The height of the frame is 400, and the height of the exported PNG image is 401, which is not equal to the height of the frame.

We need to be able to control the state of other/multiple components when setting a single interaction. I shouldn’t have to set up extensive nested variables, modes, or multiple screens of designs to get a prototype to show whether or not a button is active if a checkbox is selected. It takes thirty seconds in Axure and that includes the time it took me to make an account.

Hallo guys, just a suggestion, can you put un-collapse and collapse on right menu on the layers or frame? Maybe also a shortcut key to easily uncollapse the layer or frame? Thank you 🙂

Can we get CSS Text decoration options. Different decoration styles Gaps between Text and decoration Different decoration colors Different decoration thicknesses?

Hi everyone, I have some thoughts regarding the management of libraries and updates that I’d like to share with you. I have been working with a large design system in the last year and a half ( 100+ files including individual components, token files, variable for themes and modes etc…) and I have encountered a few workflow issues. Issue 1: Publishing a component that has broken properties It happens that some component property gets broken or missing in the workflow, but you can still publish the library where that component lives. This causes the component and sometimes the whole library to get not published, but there is no alert for that. So you realise that the component/library has not been published just when you want to load it in another file to use it. The only indication that something is wrong is a little alert icon in the property panel. Suggestion: Prevent a library to get published if something is not right and include what’s the issue with an alert message in the publish

Ability to select an entire section to use as instance swap preferred values to easily add to section options without having to go into the component and checking the newly added one / select all every time. E.g. for icon I have a frame that contains all my icon options as components. Then a “Icon” component that has each of those available in an instance swap, but the “Icon” has the variants such as size, colour, etc.

When setting up accessible UIs, one of the common requests is language accessibility, which in fact makes a lot of use of text string variables for body copy etc… One aspect that would benefit having access to string variables is text inside components, to have each instance read text strings from the variables collections. This would make language accessibility much easier to design!

Figma gave us some custom property settings for stroke. But they only did half the job. If we can add multiple borders or stroke colors…then we should also be able to assign where those are applied. Figma restricted this to only one of the color options. You have no way to tell a shape to have a red border on three sides and a gray border on the other. You know…like you can do with CSS? For example, I had to nest a frame and maneuver top and bottom padding on each size of input field so I could apply the separator line for the addon section.