Suggest a Feature

When I drag a PNG image from my desktop onto a FigJam board, I get the following error: However, the same image will upload correctly if I use the image upload flow from the tool bar, or use the keyboard shortcut. Dragging DOES work for jpeg images. This feature is important to me because I take a lot of screenshots from other artifacts to quickly compile them into FigJam for team meetings and general synthesis. I’m using Mac OS 13.0.1 and Chrome Version 110.0.5481.77 (Official Build) (x86_64).

I know there is the selection tool, however, it isn’t as flexible when working with hand written/drawn elements on the board. I’d like a lasso select tool that allows for a free-form selection with more precision.

Scaling vector by setting constraints to it is super easy and a convenient feature but what if we could do the same for text. It would be like rem built inside figma!

We recently migrated into Figma and imported all our sketch files. I created a solid DS in Figma. Now the problem is, while working on old files, It’s hard to remove a layer and place the component at the same place. It’s been so much annoying and it’s a life saving feature to have something like replace layer with component. Do you also faced same problem ? Please help me out if you have a workaround or plugin that eases this.

My colleague and I recently released this widget: Estimate Stickers | Figma Community As an enhancement we’re adding the ability for users to select different shapes for the estimate stickers. We’ve written the code and logic to switch the shapes, and are finessing the UI. Ideally we want to use the WidgetPropertyMenuDropdownItem with icons instead of words. But reading the documentation it appears WidgetPropertyMenuDropdownItem does not permit icons. Here’s a very quick mock-up of what we’re trying to achieve: We want to make the widget feel as FigJam-native as possible by copying the patterns used elsewhere in the Figma UI. Ideally we want it to look and act like this shape selector elsewhere in Figma, but with our own custom icons: Is the UI in our mock-up possible using the widget API? If not, is it on the roadmap as a future enhancement?

It’d be cool to have an interaction type that works a bit like overlays; you create an object that will follow your cursor, then link an interaction from your device UI frame to this object and set it to “Follow cursor”. Now when you preview the prototyped UI frame, the object will follow your cursor. This interaction could also offer a “Hide default cursor” option, which allows to use the object as a custom cursor, or just as a design element (like on the Frontify landing page for instance).

Problem: the design system my team uses is based on an 8px grid, ie. we want to limit sizes to multiples of 8. This is something we currently do manually and works because there is shared knowledge, however it is a small bit of overhead. Proposed Solution: Allow us to define different kinds of variables that would be usable from anywhere a size can be specified. This would help standardize things like spacing between elements when using auto layout, padding, border radii, etc. Ideally my team can have slightly less overhead when making size decisions. I have played around with both the Design Tokens and Figma Tokens plugins, but both are “too far from the metal” and the efficiency gains aren’t worth all the extra clicks and tooling.

HI all. This week, I launched a UI-less plugin command that creates component specifications including Anatomy, Layout and spacing, and Props. User requests (such as “don’t add styles to my file”) suggest that user-controlled configuration would be valued. What is the best way to enable configuration without Parameters (annoying to click through every time) or a Figma UI? My thought: publish a “Configuration” frame with a stack of properties, a default value, and other values they can choose from in a community file. Users would then place that frame into their local file, edit the config, and the plugin would findOne and read that frame as it runs each time. Is there a better way?

In my figma plugin, I did, let targetNode = figma.currentPage.findAll((node) => node.name === data.target); I can access a node in one of the layer. I am trying to hide everything and from this node, by traversing to root, to set visibility. But I get error to access parent in loop. Basically trying to do below in a loop console.log(“current page”,figma.root.name) let node = targetNode[0] node.visible=true let nodep = node.parent if(nodep?.type ==“FRAME”) nodep.visible=true let nodepp = nodep?.parent if(nodepp?.type ==“FRAME”) nodepp.visible=true

Text review plugins can only return suggestions while entering text edit mode and on the PropertyChange event type. But what if we add a text range selection event and return suggestions for that range? This would make plugins even more powerful. For example: If the user enters text edit mode and all text is selected (0, text.length) or nothing is selected (start === end), the plugin will return suggestions for the entire length of the text. If the user is already in text edit mode and selects a range of text, return suggestions for that range only. That is, every time the user selects a range of text, the event fires specifically for that range.

Currently, text review plugins can only return 3 suggestions, no matter how many elements are in the array. This limit is not mentioned in the Plugin API documentation. It would be great if the limit on the number of suggestions could be increased.

Being able to add/post comments as a voice note. (could be transcripted). The design would be the same as now but with the option to record a voice note instead of having to type the text.

Hey guys, i am new here and want to say first: I love the way we can implement plugins to figma, this is awesome, great work! I noticed the following: if I want to check a node to see whether it contains a stroke, I have to query different properties, depending on whether I have a node of type GROUP or FRAME. For example, if i want to check the node type GROUP for strokes, i am fine with if(node.strokes), because it is undefined if not set. If i check the type FRAME, i have to use if(node.strokes.length), because it is empty but not undefined. Maybe I’m missing a property that is unique, but it seems to me that this is some kind of a bug?

Instead of defaulting to Local Library when searching for an asset, it would be nice to be able to switch the default library to search. I find myself clicking “Search all libraries“ 95% of the time.

Hi all! I hope you’re having a nice week. Just a small request: I would find a separate hide/show guides option in the View menu very helpful, separate from hide/show rulers. There any many times where I don’t want to see the many guides on a document but still find value in the rulers. That’s all. 🙂 Thank you! Jeremy

I find it difficult that I have right click and select different plugins at different times which is time consuming. However, I was wondering if there was a way to minimize the plugins we use to small tabs on the top, below the top nav bar so that it’ll be a matter of one click to open the desired plugin we use for the project. Hope you guys understood. Thanks! 😀

We are building a plugin that allows users to render figma prototypes as videos. To support that we wanted to use WebCodecs API (Video processing with WebCodecs - Chrome Developers) which is already implemented in chrome. It works in most modern browsers, but to our surprise trying to access window.VideoEncoder results in undefined exception. It is however possible to access it if you specify a null-origin frame for your iFrame and serve it from our own servers. We are wondering why that is? Is there a security concern? Is it just set to undefined because it hasn’t been whitelisted as an approved browser API yet? It is a really powerful API that opens a lot of doors to creating really interesting things with Figma.

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.

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,

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.