Share Your Thoughts

Hi everyone. I have a custom implementation and it does the thing. function goToNode(pageId: string, nodeId: string) { if (!pageId || !pageName || !nodeId) { return; } const page = figma.getNodeById(pageId) as PageNode; if (!page) { // Some error handking. } const node = figma.getNodeById(nodeId) as SceneNode; if (node) { figma.currentPage = page; page.selection = [node]; figma.viewport.scrollAndZoomIntoView([node]); } } But recently I’ve discovered that this implementation is useless in case of remote components. First of all it’s impossible to acquire the page since Figma API doesn’t expose full tree of remote componens (component is hanging in a vacuum with undefined parent property). Moreover figma.viewport.scrollAndZoomIntoView() call doesn’t work as expected. It scrolls to the middle of the nowhere on the current page in the current project. Is there any workaround to make a navigation to a remote component (like native “Go to main component

It would be very cool if we could load a set of libraries like design systems, illustrations, icons, etc via the plugin. Now every time we start a new project, we have to link those libraries manually via the assets panel.

I know it’s frustrating that Figma doesn’t preview fonts or have a search icon, but it’d be great if they had a scroll bar at least. I know I can just type the first letter of the font to jump, but a scroll bar would be nice.

Hi Figma. First of all, thank you so much for introducing nested instances feature! It’s a very good feature for a team that handle design systems. It gives our consumer a clear clarification what they can do with components without the need to dig deep into the layers of the component. There’s one thing I think it can help this feature to be a lil bit clearer on the right panel. It would be best if Figma can add a separator between each of the parent group and have an indentation for the children nested instances. With this, it’s much easier to identify the grouping, especially on complicated components with many nested instances. Please refer to the image attached.

It’d be helpful to be able to see a breakdown / total of exactly how many components, variants, and styles (of each type) are in the file — which would help with performance optimisation and library publishing. At the moment there is a feature when selecting a variant set which shows the total for that set: But to get the total for the file I have to count all of these by hand. Total publishable ‘items’ are also seen in the menu when publishing to a team, but it doesn’t offer a breakdown by component, variant and style etc. It could also be a neat idea to be able to break this down by the categories the components are organised into so you can see where the ‘largest’ components are in your file that could be optimised, like in this table I put together by hand when trying to work this out for myself 🙂: For context, I just finished work on a large community component library with hundreds of components and thousands of variants (but I had to total these up manually). In tests,

I do accidentally move around comments by mistake. And whenever I cmd-z I accidentally undo the designs rather than comment move.

When I’m going back and forth between prototype view and figma file, it’s annoying that closing the prototype brings me to a tab on the right instead of the figma file which is on the left. I always need to navigate back to my figma file. Seems like a simple fix with exponential benefits.

Right now if I use a subcomponent I can only add an “instance swap” which doesn’t help me a lot of the times. For instance, if I embed a toggle component with an on/off variant there is no way for me to control that toggle switch at the parent level. More info 👇typefully.com

If a user updates a color in their file styles, it will not update gradients, as they currently can only use a Hex code. Bringing this back up https://forum.figma.com/t/gradient-color-picker-should-include-a-list-view-for-colors/11184

I like to leave CSS snippets in my design files for developers to reference. The code block in FigJam works really well but it’s not possible to use it in Figma design files which I find very annoying.

Whenever I’m previewing a specific component on Figma Mirror (for example if I’m experimenting with button interactions or states of a components), the component’s preview is always set to fill the width of my browser window and this is never the most helpful option. I want to be able to set it at 100% so I can preview my designs at their intended size. What happens (Assuming I’m previewing the interactions of a button): I open Figma Mirror on my secondary screen I select an instance of a button The button appears in Figma Mirror and fills the browser window Workaround The best workaround is for me to always have a frame I can drag a component into for previewing but sometimes this just isn’t ideal Proposed solution Outcome: Just having the ability to set the preview size to 100% in Mirror (regardless of the frame’s size) Whether this is a Figma Mirror control or within Figma’s settings, I’m not too opinionated on but having a preview scale all the time is rarely what I want. It’s

Sometimes I got tons of comments daily in my files. Would be great to have a possibility to save some of comments for later. Right now if I just read a comment and want to get back to it later Im saving comments link in trello, that very frustrating.

Right now this is only possible by creating new frames for every color/stroke position, could be great to add this feature update to the amazing recently launched individual strokes.

Hi folks, here are a few of my FigJam wishes: Curved arrow mode - to make cleaner bubble diagrams for systems thinking diagrams and large process flows Frames support - or something similar that lets me group large bodies of work together, create a playback slide set, color the backgrounds, etc. Resizable stickies - as they stand they are pretty limited; changing the dimensions of stickies makes it easier to organize them and make distinct differences for visual reference Whimsical-like history playback slider; you could “run” the playback bar and adjust the of play back and forth to create presentations Saving your layouts as templates - I use the same stuff over and over, it would be great to have a library of these Thanks for your consideration! Ben

I’d like to be able to have items fixed on scroll not necessarily as the top layer. It would help create things like parallax effects, or reveals on scroll. Also sometimes want things to scroll over a stick logo (eg coloured block that changes logo colour due to opacity effects)…

I frequently present things to clients and colleagues. Both design comps and strategy presentations. I prefer to share a Figma file for this (usually in prototype/present mode) rather than do a screen share in a video conference app because it lets people see things in a full browser window and without the compression of a screen share. The problem is I have to explain how to get them into observation mode every time, and if they click or scroll on anything they exit observation mode, often without realizing it. Then I get the “wait, what slide are we on?” question and I need to explain how to follow me again. What I’d love is a way to force observation mode. This could be an option in the Options dropdown, similar to “Show Figma UI”. With this enabled (when using this URL) the viewer would always be in observation mode – observing whoever created the URL. After the presentation I could share a separate URL that allowed them to navigate through on their own.

Describe the problem your experiencing and how your idea helps solve this In my humble opinion, the cursor in Figma has an ugly rendering. Add as much context as possible (screenshots, Figma files, mockups, etc.) Actually it looks really ugly. Ask questions to bring the community into the conversation How about to change it to something cleaner? I suggest this one, looks much better: Volantes Cursors Just compare them: And there is another nice cursor: Bibata

Initial thoughts Overall – really impressive feature that has a lot of potential. However, here are a few observations that I think are worth noting. The good The potential of this feature is huge! I spent 5 minutes making an interactive radio button that can be re-used. Bish bash bosh. When designing a long service before this feature - this tiny interaction would have taken me hours. This feature will speed up the prototyping workflow 10-fold. Great work 👍 It’s a a super easy feature to pick up. Very small learning curve. The could be better Auto-layout and nested variant interactions I’ve noticed that auto-layout components containing interactive variants that expand and collapse does not respond well. Example of component and interaction: Example of component failing to adapt to nested interactive variants, leaving blank spaces and hiding expanded states: I was expecting it to behave in a similar way to how when I toggle the nested variants in the master component within

I’m not sure if this is a feature request, a bug report, or a public service announcement. But here goes: My file has a few different pages, and I have a different prototype on each. When you launch a prototype, you expect to see the one that lives on the page you’re viewing, which is what happens - usually. I’ve noticed that if you have a prototype from the same file already open in another tab, then you will always re-run that prototype - regardless of the page you’re on when you hit the play button. It took me a while to figure out why I kept seeing the prototype from Page A when trying to play the prototype from Page B: because Page A’s prototype was still open in another tab, and Figma was just switching to that tab. A. Feature request: it would be nice if regardless of other tabs running prototypes, Figma would always show me the one I’m looking at when I hit the play button. B. Bug report: Is this the expected Figma behavior? If so, see A. C. PSA: If you notice that Figma keeps