Suggest a Feature

I am creating a bunch of tweaked interactions for a prototype with lots of buttons with unique values. But every time I type a new value for a string, a spacebar is being seen as cue that I want to close it up. But I don’t want that, I want to be able to keep typing until I hit enter (as enter closes it up as well).

Use case I have a button component which for different colors we use different text styles (one is bold the other is regular). Solution It would be great if I could just add to the button variables table a String field where I say which style to use based on the mode and bind that String to the text style of the label.

Does anyone so disappointed when we’re no longer can create a section by select multiple frames, then press the section button? Now we have to drag the section area instead of auto creating section (with padding) by default as it is in UI2.

It’s currently in the bottom right corner which frequently blocks text and frame options. A recent update moved the toolbar to the bottom of the screen, and I think the help and resources “?” makes more sense to be near that instead of blocking vital functions of the program.

I would like to ask if it’s possible to add a function for prototyping with a string variable .length method that calculates the number of characters in a string. Additionally, it would be helpful to allow setting the string.length to a specific number to split or truncate the string. This would greatly enhance the functionality of our prototype by enabling features based on string length. I also created a plugin called Input Fields to create input fields in Figma prototypes using variables. However, without the ability to split the string, implementing a backspace functionality isn’t possible.”

The main reason why the is so productive while we are building the UI going back and forth to another brainstorming application such as FigJam is takes a lot of time. So please bring sticky notes to Figma as well

It’s extremely frustrating, when enabling autolayout on a frame that already has a few elements composed, that it instantly changes the dimensioning mode (from fixed to hug or fill) without the user’s consent. This often completely changes the look of the design and requires the user to go back, re-enable “fixed” mode and set the pixel value back to what it was This always disrupts the dimensioning mode of child elements as well, causing a cascade of manual changes the user must make to reset the design to what it was. Expected Behaviour: enabling autolayout affects the positioning of the direct children of the frame to which autolayout has been applied, without changing the dimensions of the parent element Observerd Behaviour: The parent element’s dimension mode is changed (to “hug” or “fill”) the moment autolayout is applied, effectively changing its height and width from what the user set it at previously. This breaks the contract between you and the user, since the user expli

It would be ideal if I could produce a prototype link that allowed the audience to both add comment (already enabled) AND to open the inspect/properties panel to grab component specs. Currently Figma requires me to share THE WHOLE FILE and link to specific sections with the flows I want my Dev and PM audience to focus on. I don’t want them having access to my whole file nor do they want to see my whole file. To keep stakeholders focused the design team is doing so much extra effort to create series of sections and pages which is forcing the non-designer audience to learn how to navigate Figma. The effort by our designers are to organize file content for consumption of non-designers would be alleviated if we could just activate the inspect panel from within a prototype.

TLDR: Switching between pages using “Fn+Up/Down” arrow is good but if we have many pages then it’s a lengthy process to switch too often. If we remember the page’s serial number in the pages list, we can use “Fn+1,” “Fn+2,” “Fn+3,” etc., to switch between numbers quickly. If I know the components page is 3rd in the list of pages on the left panel where all the components are stored on this page then to switch to we quickly just need to press “Fn+3” . If the Mobile-HighFidelity page is 5th in the list of pages then I need to press “Fn+5” to quickly jump to this page.

It there a possibility to search and filter for Layer names in the layers/page list? If not implement this soon please. I can do this in assets but why not in layers?

I’m now working in multiple Teams. The new Figma UI doesn’t let me sort/arrange which teams I work with most, and whenever I choose a Teams, I must add another click to open all Teams. Let’s say I can sort (not just alphabetically) or arrange, hide/unhide Teams, and so on. That would be cool!

The new home panel interface is genuinely stressing me out, the home panel is not intuitive, or naturally learnable with the design language previously in the interface. As such I cannot easily or conveniently jump between teams & projects as I once did, and this is slowing me down and worsening my experience. As an educator I run between multiple cohorts (teams) and in various projects, this is now multiple clicks and extremely tedious and not visually fluid as it was before. Who did you consult when you decided to roll this change out without asking your users? Was there ANY external testing? As a teacher, I endeavour to put out good designers in to the industry but this is just woefully disappointing, I would not graduate a student who pulled this stunt.

When you get into really deep, complex UIs, layer managing becomes a real time sink in terms of productivity. Every effort must be made to help users of complex UI layouts to only focus on the depth they need. One useful tool Figma already has is the ability to CMD/CTRL-right-click to see a list of all the layers under the mouse cursor and to select only the depth that’s needed. Unfortunately, the minute you right-click to invoke the selection menu, the lowest item in the hierarchy is selected (before the user has a chance to select from the menu), causing the Layers to fully expand, sometimes well beyond the desired depth. This is actually an error in UI design. If the user’s intent with their CTRL-Right-Click is to invoke a menu, then it should not ALSO have the effect of selecting an item. That’s doing 2 different things with 1 mouse click, and that’s NEVER the correct UX choice. I’m hoping this is just a bug and will be fixed. But if it’s not, then I’d like the UI team to reconside

I’ve noticed that in UI3, dragging inside sections now moves the section itself instead of selecting frames/elements inside it. This is clearly not the usual behavior and I hope it’s not an intentional change, because it’s definitely less useful than before.

Hey Figma Community, I want to address an issue that has impacted the efficiency of our design workflow—the change in the scaling functionality using the “K” key. As designers, speed and precision are crucial, and the latest configuration update has disrupted this. The Issue Previously, scaling frames and shapes was quick and straightforward: Hit K on the keyboard. Tab to change the width of the selection. ( And the Width was linked to the height which allowed for perfect accurate scaling) However, the recent update has altered this flow: • Now, hitting K brings up the alignment panel in the scale module. • The Tab key no longer navigates to the width and height fields, making it impossible to adjust these dimensions quickly using the keyboard alone. (The User interface now becomes more of a guessing game with 1x, 2x, 3x options, Design needs to remain accurate ) The Impact This change introduces a significant UX flaw, as it hinders our ability to scale items precisely and rapidl

“Occasionally, Figma experiences a black screen and requires a reload during use.”，“The arrow keys on the keyboard do not control the movement of images within a shape.”，“After changing an image in the fill function, the action cannot be undone.”

When using Slide Decks I noticed that if I zoom out to 50% for example and then go to the next slide it shows that slide in 100% zoom instead of the new zoom I just set, even if I go back to the other slide the zoom has also been reset there. This might only feel like a problem on larger displays but it’s an annoying one and very simple to fix I would guess.

Hello there ! Just to bring back the Width selected by default when i enter in the scale mode. Indeed, i used to directly type the size when i entered in scale mode, and use tab to switch between Width or Height. Now, size multiplicator is the default selection and using tab just bring you on the anchor point selection. I have to take the mouse to select width/height parameter. Sounds like not a big deal but it used to save time and movement during my work flow. I’m not sure if i’m the only one thinking like that but modify directly width/height parameters have much more sense than the size multiplicator. Thanks to the Staff ! ☀️

When a main component has changed, label it or show a change log devs can identify.

1. Describe the problem your experiencing and how your idea helps solve this I’ve created decorative patterns with nested components and auto-layout to produce the repeating and spacing and it causes terrible performance issues which is understandable given their complexity and scale. I’ve attempted to remedy this by flattening the output as large vector shapes thinking this would to reduce the computational needs to render them with auto-layout. Unfortunately, this hasn’t helped all that much. In any file that uses these large vector shapes I find that as soon as I select a page that contains it Figma freezes up and panning around the document is very difficult (pretty much unusable with auto layout). I’m aware I can produce a similar effect using and image fill with tiling on any shape or frame but this is limited to using raster graphics as the source. Aside from the fixed resolution of raster graphics, not having the ability to set different fill colors to my patterns is another do

When CSS is displayed in px, letter-spacing will also be in px. For example: font-size:16px; letter-spacing:0.8px; Can this be done like line-height? letter-spacing:0.8px; /* 0.05em */

In dev mode, we can see “Created {time} ago”, and a button to see what changed, who changed it. But we can only know who created it if it is modified at least once. In other words, if it is created & finished within a same day, we cannot know who created it. Especially in a file where multiple editors collaborate together. I think Figma should have a text somewhere telling “Created by” near that timestamp in Dev Mode or somewhere in viewer’s Properties panel.

FRUSTRATED with the new way to handle auto layout, more clicks required to get what I need. Gone back to old UI. When enabled I expect elements to act as they would in a flex container. When using flex in code, elements don’t magically have a fixed width when you put them in a container. Adding a fixed width to something is actually a pretty rare practice. So don’t set the default to fixed. Apleeeaaasee! Would be nice to be able to configure my own preference here. E.g always set children to fill in rows.

Branching is awesome, but restricting it to org-only teams is not. Experimentation and versioning are essential, table-stakes practices in product design, no matter the number of designers on a team. Figma has always been focused on making great design accessible to and inclusive of all, but this pricing strategy is exclusionary in nature. Even if there are restrictions for number of branches, branching should be available to non-org teams. Please fix.

The newly-introduced (as of today Jan 5, 2022) Comments features seem to have dropped ID number from each Comment. Please bring it back. When collaborating in real-time over Zoom w multiple designers/developers/product folks (multiple times a day!) this now makes it very difficult to describe WHICH comment the team should be focused on. Before today’s change, the leader of the disussion would simply tell everyone that she’s talking about Comment #25 (for example). Now there’s a new layer of complication in getting people to understand which Comment you’re actually talking about, since they no longer have unique numbers.