Share Your Thoughts

Add child elements within the parent, respecting the parent’s settings. Example: When a child element is placed inside the parent that contains the (Auto Layout) settings, the child elements have absolute positioning, not respecting the settings of the parent component.

Hi guys Our team uses the Flow function in an unusual way, we add a Flow starting point to each layout, thus having a menu by layouts in the layout view (View screenshot). This is very useful when there are a few hundred layouts in the project, and giving the client access to the design-file is not always convenient. It would be great if you could add a dedicated function for this so there is no need to manually copy-paste the layout names into the Flow starting points. Please also pay attention to the numbering of the layouts in the screenshot. A four-digit number, at the beginning of the name, so that it is always visible, very good when discussing layouts, helps to avoid long explanations or naming long names, just say the number. It would also be great to make a built-in function for combining frames into groups with numbering like that, that would automatically change when rearranging frames within a group. Please think about it Thank you)

Hello everyone. Dev mode is great and it really helps to decrease hand-off pain. I found just one issue: interactions. It would be even greater if under the “interaction” section in dev mode, I could see all nested interactions of my selection. I share a concrete example: tooltips. To put it simple, let’s say I have a card component with an heading which have an edit icon button and a star icon button on the right side. I’d like to put a tooltip on the edit button saying just “edit” and a tooltip on the star saying “add to favorites”. I don’t want to make a variant for each tooltip, I want to use prototypes (open overlay while hovering), so that every card just has the tooltips I need. My fear is that the interaction gets lost and my dev colleague won’t find it because he has to click inside the component until reaching that particular button which have the interaction. It would be a charm if she could see the interaction of the nested layer right on the parent component and be aware o

It would really be great to have this feature. Kind of a basic feature i.m.o. this topic already was postet twice. And they were closed automatically after 3 Months of no reply. So no one can upvote that issue anymore and I am now forced to create a redundant thread. I don’t think that helps anyone… So consider this my upvote for these threads: Set guides with numerical input Share an idea At some zoom levels (for example, when looking at a long website layout) it’s hard to drag a guide to an exact number. It would be helpful to be able to set a guide based on a numerical input, or even have some pre-set options like center, left, right, or common web or mobile breakpoints. Ruler guides with numerical input Share an idea Hi Figma peeps, I use guides and layout grids interchangeably depending on the scenario. I can set up layout grids numerically but can’t set guides numerically. Would be cool if did. Thanks! Please leave

Copied text don’t include it’s hyperlinks, Coping textbox as SVG do include hyperlinks in anchor tag, but it transform text to path. There should be an option to copy the whole/selected text as html or markdown with it’s hyperlinks.

I would like to have a feature or change behaviour, when click-locking component specifically. Right now, when you “cmd + click” (ctrl + click) you get to the lowest element you within layers you can get. But what if I need to change state? I have to cmd + click and then got to layers and find the component in there ti change state. Image you have complex forms with dozens of input fields of different types you already prepared content for. Now go change 50-70 % of them, because you need read-only state e.g. It is extremely long way to change state of component. Would be nice to have like “option + click” or change behaviour of “cmd + click” if I hover over the component. Reason for cmd + click change is simple - you want to change specific thing and in a component, it is very likely a text OR change status. And text can be variable.

If I have 2 auto layout frames nested inside of another e.g. Main Wireframe (Auto Layout) → Side Bar (Auto Layout) → Body (Auto Layout) I want the side bar to be responsive and always scale as a % of the overall Width. I’ve been able to do this using variables but only at fixed Widths. Ideally I’d like to resize the main window and the required frame should maintain the 25% or whatever % scale. It can be done with constraints if I remove auto layout however that kind of goes against the whole point of using the power of auto layout.

Would be handy to have (design) annotations in DevMode so developers can see requirements / interactions / behaviours etc.

Notice how the animation only works when I move my cursor horizontally from within the component, but the animation doesn’t work when I move my cursor vertically across components. Not sure how to fix this.

I’m trying to make layers tidy, and when the layers count is more than 99, tidy becomes disabled.

Recently I found it super annoying that the default tab under ‘Search all resources’ changed to ‘Plugins’ instead of ‘Component’. The previous default ‘Component’ works the best for me and all my colleagues. Please at least allow us to set it as my preference. I hate it so much that I got to do the extra click to change the tab. 💢

Often I am quick searching a plugin but do not have it installed. It would save time to run my search in the Community.

Hello. I have an idea for a library search. So that there is a richer issue, and not just letter for letter. If I want to find gray-8, it’s much faster for me to write “gr8” and selected gray-8 in search result.

This already works for frames. it should work with sections.

In the new version, the right panel is divided into design and code. I think this is a very unnecessary update. In the past, you could handle both code and design in a single panel. When you switch to the code section, the tools for design disappear. Constantly changing it makes my job very difficult. Can I revert to the old version?

How many of you consider adding image trace as an option in figma when an image is shared?

Hi Figma, My team and I are enjoying using Figma’s Dev Mode. Thank you for providing such amazing features. However, we have a feedback for you regarding this mode. As you can see in the picture, the stroke width of this component is set at 4px. Yet, when we switch to the “Dev Mode,” we don’t see any information about the stroke width in the CSS, iOS, or Android sections. Has anyone else faced this challenge with their teams? If so, how did you solve it? Best regards, Sahar

please add this into the Figma export…Compress PNG

Now that we can add multiple actions to a prototype interaction (i.e. I click this and x,y,z happen), it would nice to be able to reorder those actions. As Dylan Field mentioned in the Config Keynote, the order determines how these actions are executed. Once you have actions x,y, and z, it would be nice to be able to drag and drop them to rearrange them to y,x,z for example. I’m surprised no one has suggested this yet, I searched for an existing request but couldn’t find one.

2023-08-09T04:00:00Z I organize my Figma projects based on features and my pages based on user stories. Each page within my design file is linked to a specific user story. I create frames for every requirement within the story for desktop, tablet, and mobile views. When it comes time to share a prototype, I can only select one device type for the whole page. For easier management of the page, I group my frames into sections based on device type. I need a way to share multiple prototype links, each with their own prototype device settings.

Hi, I work on a multibrand design system which has separate style, component and asset libraries for each brand. We have published a few releases to all our supported brands recently and noticed in testing that when we hit publish, users get the pop-up in the bottom right of files that consume the styles/components before the libraries have finished publishing. This has meant that rather than the entire release being stacked up before a user accepts it, there is the possibility that they are receiving only part of the update, which is obviously undesirable. For context, the ‘user’ in this case was a colleague who is also part of the same Figma team that was on a call with me as I was publishing for test purposes. We were publishing a large update that affected separate system Style and Component files, so users needed to wait for the Component publish to be complete before accepting the Styles one, which was specified in the release notes for each. When the pop-up appears, the user see

When deleting files from projects, Figma doesn’t show a confirmation dialog, making it too easy. It’s even possible to mistap the Delete/Backspace key in the keyboard and the file gets deleted without confirmation. When deleting the file when it’s open, from its own central menu, a confirmation modal appears, this can be used in other instances as well. Given that deleting a file is a disruptive action for most organisations and professionals, please add a confirmation modal whenever a user deletes a file, wherever in the app.

Instead of one giant library file, we break down our components into several files which all inherit from Core library. When publishing this Core library, it’s a manual process to update and publish all the other related library files. Suggestion: Add a secondary step to publishing with a list of all the published libraries that inherit from the one you’re currently in. Select the ones you want to auto-update and publish.

With the latest update, the flyout menu for prototype wires now hovers inside the workspace. This dialogue box gets in the way when trying to select multiple wires. Please revert this menu to appear in the right sidebar so the user doesn’t have to continually move the window around to see the frames underneath.

the big need I have is that I want to keep context of comments placed on downstream child components when I’m viewing and editing a master / parent component. another cool thing could be is if I add a comment to a master component, this special mode of a comment could show up on all downstream child components, which would allow me to question whether the comment still applies in all situations, of if perhaps the comment overlooked some edge case. EDIT: this should also take into account variants. If I comment on a component variant, it should appear on the correct variant.