Share Your Thoughts

As mentioned in closed topic https://forum.figma.com/t/bug-autolayout-resizes-incorrectly-when-it-contains-no-visible-frames/14619, Is anybody facing the same problem? Even all contents inside “trailing-section” frame are invisible and frame resizing is set to “hug”, it still has 24 pixels of width.

it would be game changer to be able to export generated artefacts with figma make to figma design  

Hey, It would be great if we could manage the z-index of some elements. Example: I 've got an element which has a built-in tool tip displayed on hover (or click, whatever) if it’s in auto-layout and the previous element is just above, this tool tip will appear behind this precedent element. The only way to make it appear on top is to place it manually on the actual layout which takes horrendous amount of time. I suggest there would be an option “take the highest z-index” or such when defining “display overlay” in prototyping mode.

When overriding a single element inside a slot in a component instance, Figma marks the entire slot as overridden. As a result, updates made to the main component no longer propagate to any elements inside that slot — even if only one element in the slot was actually changed. Expected behaviorOnly the modified element should be treated as overridden.All other elements inside the slot should remain linked to the main component and continue to receive updates.

I’m with Figma in this AI Design battle. I’d be happy to share my internal AI VScode + copilot workflow, maybe it would influence the Figma Make approach to what a designer needs from an actual “vibe designing”

Love that branches were added but would like to make some suggestions: Support sub-branches from branches. This is a really helpful way to signify milestones in an app design and allow for many avenues of exploration and iterations with the ability to only merge the branch (feature or milestone) which was approved. See example below of how I would ideally structure the process of a project

I was looking at the release notes to double check my gut feeling that Figma itself has not been getting a lot of love lately. For my personal uses that has been the case. Only vague AI related things, which might be fine but makes me feel a lot of things are left behind. The trigger for posting this was looking at “Code Connect” after reading about a “bug” in Slots that seemed to be “intended behavior” (which is weird). This feature coming from 2024 (!) seems to be in Beta still (according to the blog post). The Github feels completely abandoned. This reminded me of things like branches (total abandonement), Percentage widths, Slots that feel half baked. The whole grid thing that seems to fizz out. New UI that was not a big success (I am still scanning everytime I select a diffferent layer where things are after all these years). Still not seeing the new App layout with the buttons on the left side (my team does, not me). Etc. Etc.I was just curious, I am getting the same kind of feel

Allow offline work on files through the Figma app. This is important because internet connections aren't always available—whether you're commuting, on a long business trip, or working at a client site without connectivity. Work continuity matters. Offline support is standard for professional production tools, even cloud-based ones.

The idea is to have “synchronized sections” (see Notion Synchronized Blocks) →I often need to have the same content in several files (maps, etc.), and synchronized sections would save me from having to maintain them all.  Notion Example:  

Of course it is easy enough to lock layers but I think that it would be helpful to be able to lock pages in a fashion similar to the layers. I often place root (master, main, og?) components on a separate page and it would be nice to be able to lock these pages to keep items from moving around without intention.

While there used to be a Copy to Figma sites button, it seems that this has been deprecated in favour of “send to Figma make”.  I would request for this feature to be added back in, as well as a way to copy an entire figma file into figma sites (rather than creating a new one and adding frames as separate steps)

Within Figma Sites, you are currently unable to provide “navigate to” as a type of interaction. I am aware that you can add a link, however doing so causes an issue if you have the goals ofDoing conditional navigation (i.e. if X== true Navigate to A, Else navigate to B) Changing a variable, and navigating through the same button (e.g. set Y to Z & navigate to C)1 because navigate to/link to is not available in the interactions (where conditional is found) & 2 because if you assign a link, then onclick is removed as a trigger for interactions In terms of both, I accidentally used a workaround by copying a frame from core Figma into Figma sitesHowever, this is not convinient/intended, and I worry that it may create issues with future versions of figma sties.

The corner radius tool is great if you want to make rounded corners but what if I wanted to make sharp, folded or clipped corners like in the shape below?The catch is that when resizing, the scaling and the angle for these corners should stay the same. If you simply create a shape like this, it doesn’t really scale well if adjusting only the height or the width - the angle of the corners suffer. Has anyone figured out a solution to this or is this something Figma could implement perhaps?

ProblemWhen using stroke-based icons inside nested components (e.g. button components), resizing behavior in Figma causes major inconsistencies:• If the icon is a component, it keeps its original size when the parent resizes• If constraints are set to Scale, the icon scales visually but stroke width does not scale, causing icons to appear heavier/darker• The only way to get correct proportional scaling is using Scale tool (K), which does not work with Auto Layout or component resizingThis makes it extremely difficult to build scalable button components using stroke icons.ExpectedResizing a component or instance should optionally behave the same way as Scale (K):• Stroke width scales proportionally• Corner radius and effects scale correctly• Works inside Auto Layout and nested components Proposed solutionAdd a global or per-object option similar to Adobe Illustrator:“Scale strokes & effects when resizing”​This would:• Fix stroke icon inconsistencies• Enable proper scalable icon usag

Use case: Once an advanced UI has been built , users want a way to quickly select nested components in order to modify their properties and attributes. In this stage of design, designers are less interested in manipulating sub-elements of a component, and more interested in selecting the component itself to modify properties and variables. Current challenges: the deep-select modifier (CMD/CTRL) is currently the most efficient way to access deeply nested items, however it is fairly indiscriminate and will often select the deepest nested element under the cursor. With complex components this often means a graphical element like a frame or a text element, requiring the user to step out of the hierarchy, often a number of steps, before arriving on the parent component, or they must use the mouse to then select the parent component from the Design properties panel. Recommendation / Request: Provide an optional modifier key to be used while deep-selecting to restrict selection to only compon

ProblemThere's no plugin or REST API that exposes a fresh view of which team libraries are currently subscribed to by a file. After a user adds or removes a library mid-session, every documented and undocumented signal continues to report the prior subscription state until the file is reloaded. This makes it impossible to write a plugin that correctly classifies orphan references (variables, styles, components from libraries no longer linked to the file) without asking the user to reload Figma after every library change.Use caseWe're building a plugin that scans a file for orphan references — bindings to variables/styles/components from libraries that aren't subscribed by the file. The orphan signal we use today is figma.teamLibrary.getAvailableLibraryVariableCollectionsAsync(): any remote collection whose key isn't in that response is classified as orphan. This works perfectly when the cache is fresh (after file load), but breaks silently when the user changes subscriptions mid-sessio

I work for both desktop and mobile screens and I would like to save custom frame sizes and have them under a custom category. basic desktop sizes like 1366x768 is not available in the presets and the desktop category only has Mac screen devices as options.

Allow the users can move the new toolbar through the canvas, that today is fixed underneath the page. I liked the new version but I believe some extra flexibility on it would be welcome.

Figma is the most intuitive tool I have ever used and I would love for Figma to expand into web development! Publishing a website directly from Figma would be incredible!

When adding components to a Slot and attempting to surface nested properties I see a message that nested properties can not be surfaced with Slots. This severly limits their usefulness to us since we are creating multiple composable components using sub components with properties and having to drill in to each instance in a multi-item Slot is very time-consuming.

Just a thought, but the effect property in the annotation is very vertical. In general, when using variables/tokens, why are they not displayed in the annotation? Dev-team is referring to the token instead of the raw value. 

It would be great if I could use my right mouse button to drag the page like you can do in Miro. 

Hello,I’m really excited about being able to use AI to edit our app screens. It would make important stakeholders able to work by their own.However, for now, the results I get are far from being usable.First, despite the announcement, I have no icon related to this… strange.But it’s accessible through the cmd-k menu → “first draft” or “make a change”My first “first draft” was a banger. With only a vague prompt, it created a neat design with nice architecture (better than those of most of designers I’ve worked with ;-) )But as soon as I use the “make a change” menu, which is where the work begins, it’s really bad. Most of the time it doesn’t stick to the selection I gave and change something else. It doesn’t understand some basic command (selecting a menu, I just ask to add 2 entries… it renamed the others and change the colors...).So, am I missing or mis-using something? Do you have similar experiences or much better?Peace,Franck

I cannot understand the following. Figma Make makes a destructive mistake and uses credits. It then uses additional credits to fix the mistake it made. If it applies the wrong “fix”, it uses even more credits to address the issue. If it recognizes it’s addressing an issue caused by the AI, why does it continue charging a user to address the problem. This is my hugest pain point with this product and pricing model.

Since a couple of weeks Figma Buzz is auto-naming the frames it creates when BULK CREATEing. It simply adds 10 (or something) characters from each CSV-Tag and pastes them in.Please add the possibility to deactivate this feature. It messes with our current workflow and forces us to add additional steps. Would also be nice to be able to fine tune this to our needs (i.e. choose what tags should be used)Also: there seems to be no documentation in terms of release-notes for this.