Share Your Thoughts

Proponho a implementação de suporte a Markdown nas propriedades de texto dos componentes no Figma. Essa funcionalidade permitiria aplicar formatação tipográfica de forma declarativa e padronizada diretamente no conteúdo textual (ex.: **bold**, _italic_, # Heading). Além de reduzir a dependência de estilos manuais, isso facilitaria a prototipagem de conteúdos dinâmicos e a integração com sistemas de design tokens. O parser de Markdown poderia ser implementado como uma camada de pré-processamento antes da renderização, garantindo consistência entre documentação, prototipação e handoff para engenharia.

I use nested auto layouts for my tables: The table is an auto layout containing columns, and each column is an auto layout containing cells. I want my table to be responsive, so I set all columns to hug, except the last column, which is set to fill, so that the table spans the whole width of its container. But in smaller screen sizes, if the screen width goes below a certain number, the last column gets clipped/truncated as it’s on ‘fill’. So I set a min-width to ensure it is not clipped. But, right now I need to hard-code the min width. It would be ideal to set the min width to ‘hug’, so that I don’t need to hard-code it or change it every time I update the contents of the last column.

Hello, I am new to Figma but could not notice how difficult it is to navigate.Everything is so tiny and so difficult to move around and enlarge.Seems like UX is not the strong side of Figma. Thanks.

There are times I want to have Figma Make use csv or json files for data retrieval. Currently, the AI has to build a UI component in the preview window to allow this to happen. I should be able to upload files in the chatbox.

Hey guys! I'm a product designer and a Figma lover. For along of those years, I saw Figma grown up and become even better, bringing to us designers a lot of new possibilities to work. But this is my first time that I want to request a feature ASAP, since creates a lot of pain. Hope everyone see this topic as something really useful too.So, I usually works on web applications and thus I need to design both mobile, tablet and desktop version of the web pages.And, when we speak about Design System, we need to make sure that our components will adapt on each screen, no matter the viewport size.So, bringing this discussion to a real case: I made a component for my DS called “chip” with some variants as we can see on this print: The width’s component need to follow their inner content to keep growing on the sides as we can see:but this growing effect (which is possible glad the ‘hug’) need to stop when reach the max width from the chip’s parent container and this, Figma can’t help me. So, th

Would be really nice to have line hops for when creating complex IA charts or other interaction maps, site maps, etc. Sometimes it’s hard to not have 2 lines cross and having a line hop is a really nice feature. If you’re looking for an example, Omnigraffle has had this feature for quite a while.

Im creating a prototype and would like to link to live pages on our site without having the User in the test have to see the “Leaving Figma Warning” page. My concern is that it takes it breaks the illusion of an actual experience. Is there a way remove this middle page from the experience?

When updating a component from a library and clicking “update all” (either all updates, or all instances of one update), Figma will immediately tell you that the updates have been applied. But especially in cases when there’s a lot of instances to update, they clearly are not, as the whole client will slow down to a crawl for a considerable while and the updated versions keep slowly changing in the view. Could you maybe add a spinner and a message that tells me when it’s actually done and I can work again.Also the ability to set some frames/pages to ignore updates would be nice. I can have things I don’t want changing even if I update the rest of the page. Skipping those instances by hand every time is a pain in the ass.

It would be cool if you could right click and fill container and hug content and ignore auto layout. These are used a lot.  

Make sure to read the updates to our Figma Education plan and let us know in this topic if you have any questions or feedback. A few quick reminders:If you need help with a specific account or file issue, please get in touch with our Support Team. A note on Forum Guidelines: Posts that veer off-topic or become unproductive may be moderated to keep the focus on the product at hand. Keep feedback focused on the updates to the Education plan — this helps everyone follow along.

I am actively using Variants, but there is not enough search in the Variants selection list in component. In my Design System I decided to design one basic component: 1 button, 1 input field, 1 icon … etc. I implement the rest of the variations and states in Variants. I’ve in my base 16px Icon component 34 Variants of icons, in base 24px Icon as many. Search bar would be of great help: Does anyone use Variants like me? How did you solve this navigation (Search) problem? 😊

So many times have i accidentally closed the file i am intending to open because of your decision to surface the close X on hover for a tab i am not active in. Chrome does not do this. Please remove it. Make close X only appear for active tabs

Hello Awesome People! First of all, I’m sorry if this has been asked somewhere already, I tried searching but didn’t see anything. Is there a way to know what design files have detached a component? Here’s an example scenario, I open up a DS file and navigate to the library analytics I click to view more details on a component which says it’s got 3 detaches I arrive on a screen with all the variants listed for this component, I click on one which states it’s got 1 detach I then arrive on a screen which is listing 16 pages and I’m not clear why wanting to just find the file that has the detached component. I hope the above makes sense, thanks in advance for any pointers here 😊

As written in the documentation (Prototype interactions and animations) the destination of a Scroll to action can only be an element of the same top-level frame. But with this limitation it is impossible to prototype a common navigation pattern. On one-pagers there are often floating menu for intrapage links. E.g you have an hamburger icon that opens a menu overlay from where you can scroll to a specific page section. This can’t be realized with an Figma overlay because of the restrictions mentioned above. There is a workaround, but it seems that it only works because of a bug: You can set the menu overlay as an child of the top-level frame of the one-pager, define the Scroll-to actions and then move the menu outside the frame (as an separate top-level layer) to show it later as an overlay. By doing this all the Scroll-to actions still work, but when you change an action the target will be rested and the navigation is broken. Working Example Maybe you can remove the restrictions that t

When you delete an element in a nested structure, you lose all selection. This means if you want to continue working around that level, you have go dive again to that level (double-click, double click, double, click, double click…) Deleting an element should auto select the immediate upper level to stay where we’re currently working Or auto select the previous element in that hierarchy maybe, or the next one. But staying around there, not going back to root level.

Hi Figma Team!I’d love to request a small but meaningful feature: Could you please make Figma remember the UI state (e.g. when panels are minimized) across sessions? Right now, even after clicking “Minimize UI”, the left and right panels open again after restarting the app. For those of us who work in a clean, focused canvas — having to manually hide the UI each time is a bit of a chore. Would be amazing to have an option like “Remember UI layout on startup” or “Start with minimized UI” in Preferences.Thanks for all your hard work — Figma is awesome! 🙌

Hey!I’m working with assigning primitive color variables to semantic color variables and sometimes I’m not sure which color is the right one. If Figma shows the hex color value, when hovering the color swatch, while selecting the color variable I want to use would be SOOOO helpful.  Thank you!

Hi everyone, I use connector lines for my flows, but for many months now, they have suddenly stopped attaching correctly to the right-side connection point of an object. With every Figma update, I keep hoping for a fix, but the issue persists.This only happens on the Mac desktop app. I often have to switch to the Chrome browser just to make this adjustment. It's frustrating, I know!It's also sad to see that this bug was reported here months ago, almost a year now, and there is still no resolution... I hope this gets some attention soon.  

So I’ve seen similar posts before, but I’m putting this out there because its something that needs to be implented.Let me give an example, I’ve got a component for showing to elements side by side, one of the elements is a contact form, said contact form is also a component of its own.If I place a component instance of the layout component it only shows the properties for itself and not its children.It would be so useful if it could also show child properties.I would suggest showing “Parent/Current Component Properties”, a divider below it and then you list all properties the user in question added to it.Then if there are any child components you show “<CHILD_COMPONENT_NAME>’s Component Properties”, another divider and then all the properties that child has. Repeated until all child component properties have been listed.Of course someone could make a ridiculous setup where there’s like 10 - 20 child components that are each a child of the other child, which could create issues wh

I feel a little stupid, because the app introduction says it is possible:Figma Help Center But I cant quite figure out how this works? I can log in with my private account but it only has one workspace, same goes for my company account. How do I sign in with both accounts at the same time?

Add the ability to add text-wrap: pretty and text-wrap: balance so that more options are available to ensure more flexibility to how text can flow/reflow and reducing hyphenations and word orphans.

We’ve found annotations to be an incredibly valuable way to capture ideas (like animations) in a clearer and more structured format compared to comments. However, it’s difficult for us to justify requiring a paid developer seat just so clients and collaborators can view these notes. Many of our projects involve multiple client stakeholders, and it’s not practical to purchase additional seats for everyone who needs visibility. The introduction of annotations was such a helpful improvement for collaboration, so it’s a bit disheartening to see this functionality restricted. We’d love to better understand the reasoning here, as it feels like a step backward in terms of accessibility and client collaboration.

Hola, ¿cómo están?El título del posteo es autoexplicativo: lo que estoy pidiendo es que independientemente de cual sea la variante por defecto del icono, en el panel de assets se muestre la variante de mayor tamaño o en su defecto algo que facilite su visualización (por ejemplo, un factor de escala de 2x automático).En su archivo de la comunidad “Simple Design System” lo que uds. hicieron fue poner por defecto la variante de mayor tamaño para que en el panel de assets se viera con mayor tamaño.Como esto es algo que es más bien un “hack” lo que estoy pidiendo es que deje de serlo y pase a mostrarse los assets en un tamaño más accesible sin necesidad de alterar el orden de las variantes.Esta solución solo la imagino para iconos, porque si bien podria aplicarse a componentes pequeños seria dificil de predecir el resultado para componentes de mayor tamaño.Este posteo está en el espiritu de la pregunta ¿cómo podemos mejorar esto?No tengo la solución, pero si la necesidad de poder visualizar

Is it compulsory for the connector to snap to the edge of the screen? what if i want to show connection between specific elements in 2 different screens ? Also please provide good connectors in Figma as well  

When working with local variables and tokens I find myself constantly opening and closing the local variables panel. It would be nice to have a shortcut added for displaying and hiding that panel. If there is not a shortcut added in first version, then this action could be listed in the MacOS menu bar as a command, so that a custom MacOS shortcut could be added,