Suggest a Feature

Maybe I want to show width @75% or width @50% so I can show more of the depth (height of the page) in one view. I think it would be nice to have other options for how we show prototypes.

I am currently working on color updates to our UI kit and have noticed that not all of the colors are updating when I drop a screen from one variable mode to another, therefore I cannot accurately look at my color updates side by side. This feature seemed to be working fine on Friday.

Line height and tracking variables scoped to “Text variables” are not accessible when manipulating text props:

It would be nice to have a composite style option that would allow one to define which variables should be used to create a card for example, only having to apply a single style (similar to how typography allows for bundling of multiple variables). This would eliminate the need to “hunt” for variables to either apply them correctly, and/or fix where a component that does not follow the established/agreed upon pattern.

I like to add a feature to the wishlist: The hover event is very “aggressive” and reacts instantaneously. I have an accordion which expands on hovering. However, it makes it hard to scroll the entire list. I wish I could set a delay time for the “on hover” event which serves as a sensitivity setting. You would need to hover over a specific object a certain time (= user setting in ms), before the event is actually triggered. This would be absolutely fantastic and is hopefully not hard to implement.

Make a modal inherit the mode of the frame it appear in. Use case: I am creating a prototype using variables, the prototype has a button that triggers a modal. Easy enough but here’s the issue: Although the modal’s mode is set to Auto it does not inherit the mode from the frame it appears in. I will be great if the modal can inherit the mode of the frame it appear in.

Opening comments to all viewers is a problem for most designers since stakeholders or clients can grill them by commenting online. Also, some companies want to drive all feedback to ticketing systems, and Figma comments can impact their processes. Adding a “Commenter” role would help differentiate between those who need to be informed (viewer) and those who need to be consulted (commenter). Please consider this feature. 🙏

During the process of writing comments, the cursor will always jumps to other positions inexplicably. I use my keyboard doing the comment imputing process, but during that process, especially when I edit the comment, the cursor will suddenly jump to other lines, make the new typed contents added to the wrong places. And it will not staying at one place, in the other seconds, it will jump to another place.

The Frame and Rectangle tools in Figma share similar properties, such as fill and stroke, akin to the SVG format. However, adding more strokes doesn’t seem to be particularly beneficial. For instance, consider creating an input element have deault and focus states like this: Default state: Focus state: In CSS, the border and outline properties are used to achieve this effect. In contrast, Figma utilizes stroke and drop shadow effects to create a similar result. It might be beneficial to separate the stroke in Frame into border and outline properties.

hello and thank you for the support. He is the situation. I have a personal Figma account but I also have an account with the company I work for. 2 different emails and 2 different account. one day, I was trying to access a file from the company i work for and for some reason didn’t have access to it, so I clicked on the “request Access” button. I didn’t realize that i was logged into my personal account at the time. access was granted, and I then realized the mistake, so I went in and deleted the access to my personal one. The problem I am having is that everyone at my job is still able to @mention my personal account. and not just on the file i was granted access to on ALL the files within the organization. How do I remove myself entirely from this organization so that no one can @mention my personal account anymore?

The way Variables and Libraries are displayed in the UI are extremely confusing. I just spent a day looking at MUIs design kit to figure out where and how variables and colors and libraries are edited, displayed and linked to one another. I think some changes are necessary. The terms ‘library’ and ‘variable’ should not be used in multiple panels to describe various objects/functions. Use the term ‘Library’ to only refer to a set of file components, variables, styles etc that are published to be used in other files. I have no idea why the word ‘libraries’ appears in the left panel and in the selection colors modal. The colors modal should deal only with color styles. It is very confusing to have a dedicated Variables modal, and also have the option to add a style or variable in the colors panel. Make the colors modal a default pane or be able to be toggle on to display as a view setting. Users should not have to click on a color selection to access this modal to view their proje

I find myself frequently working on files which require Boolean operations (union, subtract, etc). Because of the placement at the top of the screen, the Boolean button dropdown is slightly inconvenient when working on bulk/repetitive tasks on a large monitor. Operations such as Mask and Flatten have keyboard shortcuts, but not the Booleans. The boolean operations are also not discoverable in the right-click menu. I can use Quick Actions to search for a boolean operation if it makes sense to do that instead of moving the cursor, but it would be nice to have a direct keyboard shortcut.

Hi, Is it possible to get an optional overview to recognize which components/objects are affected at which point when the library is published? When updating the library, I can compare this and also make a decision, which is very helpful 😉 Thanks a lot

Hey Figma team, My workflow consists of a lot of remote work, and I end up going through the comments while just hovering upon them. Due to this, I miss out on reactions added by fellow stakeholders over the shared feedbacks. Can you show the reactions upfront over the bubbles? Would be great to easily go through these comments…

Hello everyone, With exciting new features, I try to create a new boolean way to show/hide elements with a simple click. I successed to do it with an only one element : Button click : show dropdown list Button click : hide dropdown list. And THAT IS PRETTY AWESOME for now ! Now I need to step up with an another concept : Button click : hide placeholder & show selected products To avoid using 2 boolean variables, I tried to do it with “Mode”. So I created a new boolean variable “selection_enable” to true for my “Basic Mode” (show an empty cart) and to false for my “Event mode” (hide my cart’s selection). My goal : if “selection_enable:Basic” == true : set false to my “selection_enable:Basic”, set true to my “selection_enable:Event” Else : set true to my “selection_enable:Basic”, set false to my “selection_enable:Event” Problem : When I use conditional feature on Prototype and I select “Set variable”, I can’t choose the variable’s mode for the first selection, only for the seco

Annotations in dev mode are very helpful. However, what would be even better is the ability to surface annotations in prototypes. While Figma is a very powerful tool that comes at the cost of simplicity to the uninitiated. Most of our design consumers/stakeholders are not familiar with Figma and rapidly become overwhelmed with the interface. To help mitigate this issue we use prototypes almost exclusively to simplify the deliverable. The ability to surface annotations in the prototype view would solve several of our review and documentation issues.

Not sure if this has been proposed or not, I couldn’t find it in the forum, but file management and ‘source of truth’ is for product teams is always a hot topic. I can see having the option to connect prototypes across feature files allowing for gains in performance, file management, and feature versioning. How I imagine it would work, is when in prototype mode you select ‘Navigate’ and you have the option of file or frame. If file is selected, you choose the file and the desired prototype flow. Then Figma generates the prototype, the generation may have a different experience than a single file generation due to processes but that could be okay. Again, it might be something already in the works, if not, it might solve a mighty problem for some teams.

My (large) team uses hundreds of libraries, and we try to rely on Library Analytics daily to improve our design system. It can be quite unstable at that scale, with the modal being super laggy and unresponsive. It’s very painful for us to actually employ the data because of the tool-- it would be great for analytics to live in a dedicated tab with more fully-featured UX so that page load isn’t having to worry about populating a few hundred Teams (large org) in the background/at the same time. In addition, it would be !LIFE CHANGING! if there were a way to export the full data-set for libraries to CSV! Create a tagging system, allowing the user to tag library files within the org as being part of the dataset/design system. Then export to CSV: Columns: Total Instances Inserts (at current intervals, or use the tool to customize intervals before export) Detaches (at current intervals, or use the tool to customize intervals before export) Detach Rate Usage Rank % of Instances Insert Survi

Currently, it is only possible to create colour variables using a HEX value Can the other colour modes be added - RGB, CSS, HSL, HSB please. Adding the Alpha would be useful too, so that brand design systems can be fully implemented. Thanks

when prototyping and drag and drop is not an option (e.g. because frames are just to far away ;] ) it would be awesome if the items in the selection menu had a free text filter to find the desired frame quicker.

I’d like to request a feature in Figma where when I update a library or a component, it takes some time to load. During this loading period, I switch to another file to perform the update or keep working on next task. I wish to have a loader displayed at the top of previous file tab to indicate that an update is in progress. Once the update is complete and the loader disappears, I can proceed to update library in Figma. Otherwise I need to back and forth to both tabs to see whether the previous file published or not.

When linking a design to Jira using the plugin, the “mode=dev” portion of the URL is getting cleared, which results in all links opening in design mode by default. Given that the Jira x Figma plugin is largely for engineers to access designs, I would prefer that Figma links preserve the “mode” URL parameter so that my engineers don’t have to “turn on” dev mode every time they open a file.

Dear community, I tried to find an answer in existing topics but without success. Sorry if I just didn’t find the answer … My problem statement: I used to work in miro in that way, that I created boards with well structured frames and then I could export them to PDF with one page per frame. By that I could set up specs documents with lots of contents like in PPT or whatever have you. Now I wanted to switch to FigJam to have designs and specs in one project but I’m missing the option to create PDFs out of FigJam with one page per section. Who can help me out?

There is an issue with “Preferred values” in components part of library files. When copies of such a library are created, the components preferred values keep pointing to the source library file. For example, say we have a “Source Library” with an “Icon” component in it. We set the component with preferred values for icons in that same library. If we create a duplicate of that source library, rename it to say “Instance Library” - then the preferred values in the “Icon” component from that instance library will still point to the “Source Library”. There is no indication that the paths to the preferred values are absolute and this might cause a lot of confusion. Here for examples is the " Preferred values" documentationFigma Learn - Help Center I would say the paths to the “Preferred values” should be relative, when set to local components.

When closing files in the desktop app by using the ⌘+W hotkey, the behavior is rather erratic. Sometimes it closes the file and opens one that is adjacent in the app bar. Other times, it closes the file and returns you to the home screen when you have many documents open. Other times it closes the file and takes you to the last file that is open. I’d prefer it to consistently move to the next file to the right, like in a web browser.