We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
🎉 Welcome to the Figma Forum! 🚀
Find solutions, get advice, help others.
I'm encountering an issue updating the Chakra UI - FigPilot plugin to version 16. The error message reads: Could not publish plugin: Bad request. The upload API call appears to be failing, but there are no visible form errors. The original library author, Segun Adebayo, has given me the necessary rights to update the plugin. Please advise on how to resolve this issue.
Hello, I tried Figma slides to re-create my portfolio, which I had already created in Figma, because I was attracted by the possibility to quickly reorder the slides. However, I noticed a problem: while I can create internal links in Figma slides which allow me to jump from a slide to another, when I export said slides as a PDF, the internal links are substituted with external links which jump back to the Figma website when clicked, instead of allowing you to navigate through the PDF inside your own pdf viewer. This is a problem for various reasons: you can’t easily navigate around the .pdf offline, since each time you click the supposedly internal links you instead get redirected to a web page; the offline .pdf and the online version can be out of sync. Meaning that the offline versions, which may be several and have different slide orders or different elements (it’s common practice to slightly tweak a portfolio when you send it to different clients) will all point to the same figmasl
Hi. I have a question, is it my error or is it more of a rendering of the image when prototyping? I have a project, I divided the website sections into individual frames. I then “wrapped” these frames into one large frame. They are aligned perfectly every single pixel. Unfortunately, in the prototypes view I occasionally get such a thin gray line between the frames as below in the screenshot. How to deal with this?
How do I access the project when this comes up? Uh oh… we can’t open that file We can’t open this file because WebGL isn’t supported, or is disabled, in your browser. If your browser supports WebGL, check out this help article to find out how to enable it.
Hello,I am trying to purchase a professional plan for my personal team on Figma, but it shows this message when I am reviewing the billing info: Your payment method’s address is in a country that can’t pay in EUR. Please use a different payment method. My bank account is in the Czech Republic. Sadly, I am on a tight schedule.
Hi @figma_admin Although CSS grids are useful for consistent box sizes and much more. But inside Figma, I just noticed the width of 12col. grids with 20px gutter are varying. These were supposed to be equal.But these are same when we change gutter to 24px, the problem arises when we use gutter 20px in 12 col-grid.I attached ss for clarification.Have anyone noticed this before?
Hey everyone, I’m trying to create a heatmap feature in a custom embed that tracks where users click in Figma prototypes. I’m using Figma’s Embed Kit 2.0 and specifically listening for the MOUSE_PRESS_OR_RELEASE event. The only coordinate-related fields I see are: nearestScrollingFrameMousePosition nearestScrollingFrameOffset The thing is, in some prototypes, nearestScrollingFrameMousePosition is properly populated, but in other prototypes, it stays null (even though I do have scrollable frames). Here’s a stripped-down version of my code if (event.data.type === "MOUSE_PRESS_OR_RELEASE") { const figmaEvent = event.data; // as MousePressOrReleaseMessage const { nearestScrollingFrameMousePosition, nearestScrollingFrameOffset, presentedNodeId, handled, } = figmaEvent.data; let x = null; let y = null; // Attempt to get coordinates from the "nearestScrollingFrame" if (nearestScrollingFrameMousePosition && nearestScrollingFrameOffset) { x = nearestScrollingFrameMousePosition.x + nearestScroll
For some reason after the latest update Figma mouse wheel scroll up/down is not working properly. Let me describe the problem I’m having. When I used the mouse scroll wheel (scrolling up and down) before the latest update, it was just scrolling up/down. Now, sometimes instead of scrolling up and down its zooming in and out. I’m using Macbook Pro Max M1 2021. Please, let me guys know if you have similar issue or its just me. Maybe its related to the mouse firmware update or something or its a bug I’m not really sure. Thank you!
Explanation When creating a component, with variable text as a property and filling its text with 2+ token variables (with 2+ modes) sourced from “local variables”. Instances with text variants (different text content) break on a “local variables” mode change, resetting its text content to the component property default & forcing it to stay that way (unable to change) Replicate Create 2 local variable with 2 modes Create a component with text (text content as a proeprty of Component) Make text from component have different colors sourced from variable of step 1 Create an instance and change its text content Change variable mode (at instance “Appearance” design section) Text Content gets resetted to orginal component default property & its unable to change Example
Hi! I currently use “Professional” plan, and I purchased 2 seats, for me and my developer. My question is - Should we both have “Professional” plan so that my developer will have access to my drafts(with all the Properties visible, etc.)? Or I can just have the “Professional” plan for myself and give my developer editing rights? Or may be my developer should be on the “Professional” plan (and have access to all Properties), while I stay on the basic plan? Just trying to figure out the best option. Thank you!
One of the last remaining pain points that I encounter in most of my projects when trying to set up components to be responsive across devices, is needing to be able to define a fixed aspect ratio for responsive images. For example say I’m creating an instagram or youtube feed where the images/videos are 1x1 or 16x9, It would be great if we could lock the image layers aspect ratio to that. Unfortunately in the current state there is no way to have those images retain their aspect ratio’s on a responsive screen by using the fill property or left and right constraints, it would be amazing if responsive components respected a locked aspect ratio (or something similar) on shape/image layers so image/video heavy designs could be more accurately responsive.
Hello everyone, I’ve created icons, all vector layers with the same name, and every icon has a variant of sizes - small (16px) medium (24)and large (32). They also have round/sharp Boolean property. I’ve created buttons, also with size variants with matching names and sizes. There’s also variant for only label, only icon, left icon and right icon. There’s also instance swap for every icon size. I also have the icon as nested instance. So I take an instance of the button and I change its size, then I change the icon - lets say from “search” to “plus” for example - but if I want to change the size of the button, the instance swap return to its default icon instance. What should I do, or what did I do wrong?
APIs, guides, plugins, and more.
Find a virtual event that speaks to you.
Find answers, learn more.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.