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.
Find solutions, get advice, help others.
Good afternoon)) When transferring a component to a new file, it still refers to the previous file. How do I link to a new file? Tell me, please.
How to remove or turn off an AI option attached to a frame ? Or to see in the design settings if AI tools are actively used in the selected element ? For exemple, I was trying “Replace content” in a frame, when I dupplicate I now can only do “Duplicate with new content” and can’t turn off the option, even when removing the autolayout and putting it back.
The issue being faced today: I want to have preferred values only show up under the instance swap feature. Not searchable in the assets panel, as these are typically sub-components that I don’t want to be used on their own (examples: a dropdown menu used in a global navigation component, the vector for an icon used to instance swap in an actual icon component to control the sizes via icon properties, a single segment used inside a donut chart, pre-configured links or buttons commonly used inside a bigger component to make it easier to select from a pre-set). Why this isn’t possible: Unpublished and hidden components are treated the same in Figma. Hiding/unpublishing a component in Figma is currently the only way for it to not show up in the assets panel. Hiding/unpublishing a preferred value leads to additional issues: Preferred values cannot be selected by library consumers if they are unpublished. Preferred values must be published in order for updates to be available to library cons
I am confused how x and y coordinates for elements with “Ignore auto layout” on are displayed.The coordinates are intuitive when you choose constraints left and top. I was expecting them to change when you choose right, bottom, center or some other value. In this case I would expect them to display the value relative to that reference point. Something that sticks to the bottom right corner, should not display the distance from the top left corner (as this is a total random value, that will probably be different for responsive components). I mostly layout with values and rarely by dragging elements around the canvas and it is cumbersome to calculate those random values that do not reflect the intent of the design.CSS works with top or bottom and left or right coordinates respectively. Is it just me, or do you feel the same way?
Hello. Is there a way to stop Position > ignore auto-layout from removing the frame/object from the flow of the document/parent? All I want to do is z-position a frame -20px above the object above it. Easy to do in HTML and CSS. Absolute pain in the dick in Figma. What do people do to maintain a proper auto-layout? Thanks,Will
Hi! I’m testing a site built with the new Figma Sites feature. I’ve set the top navigation bar as a sticky element and made sure it’s positioned at the very top of the layer tree. In the Layout panel, canvas stacking is set to “First on top.” Canvas stakcking settings It looks fine on Figma and Chrome(desktop & laptop) On Safari and mobile browsers, the sticky navigation bar appears underneath the hero section content, even though it’s set to be the topmost layer in the design. On Chrome (desktop & laptop): everything works as intended — the GNB stays sticky and always remains on top. On Safari (desktop & laptop) and all mobile browsers (Safari & Chrome): the GNB is sticky, but appears underneath other layers and is partially or fully hidden. Is there a workaround or fix for this issue? Thanks in advance!
With the new update, we have a great new feature, but unfortunately, it’s not usable with our component structure. Exposing all props of a nested instance also exposes props that we don’t want in the context of the consuming component. What if we could also select which properties to expose? This would lead to a cleaner sidebar with only valid props.
Whenever I export a PDF and try to print it from Preview, the sheet of paper comes out completely blank. I can only print Figma PDFs from Adobe Acrobat—when I do, the issue doesn’t occur. But that only solves my problem, not the issue for the rest of our team, who don’t have Acrobat. I notice a similar issue when placing the PDF in InDesign, the page also stays blank there, which makes me feel that something is wrong with the PDF itself. Is this a bug? Is there a workaround that doesn’t involve exporting as JPG/PNG? Additional information: Multiple team members have this issue, but not everybody. The PDF shows the full design in Preview. Printing as a JPG/PNG works fine. The issue also occurs from FigJam.
Hi, I’m not sure if this is new since the May update, but I wonder why “empty” (all elements hidden) Auto Layout Frames keep the size of the last hidden child (and I do not mean last in the list, but the last element to have been toggled out of view by the user), making them not-0px high even with nothing in them. See here a file with a Frame with three hidden rectangle: the Frame keeps the size of the last child rectangle to have been hidden. When adding a 0-px Frame to the AL frame, and toggling this 0-px Frame off last, the container goes 0-px. In my opinion, empty AL Frames should have a height of 0. What do you think?
Download code button I spotted the "Download Code" option in the upper right corner of the editor, but I noticed that there is no "package.json" file. Is there any documentation or a way to run these projects locally using my own IDE?
In prototype mode, the hover effect (“while hovering”) sticks and does not disappear after hovering over an element. As a result, when hovering over several objects, all hover effects remain on the screen. What is the bug? : worried: Closing and reopening the prototype helps solve the problem. But after some time, the bug may appear again. It looks like some kind of memory problem, in general, prototypes and files take a long time to load and sometimes slow down. It’s very unpleasant to work. In Figma via macOS app
Since a week I am having trouble with exporting PDF’s in Figma. The export works fine until I want to import this PDF into Adobe Indesign or an online print tool. Both apps failed to load the Figma PDF. I have send the files directly and the service replied they are having issues opening my file. The strange thing is, I can open the PDF in Mac preview, in an internet browser and I can import it in the Gimp image editor. So sometimes it works, sometimes it don’t. I am using the latest Figma 116.16.13 on Mac OS Sonoma 14.0.
Currently components are published as is on the website, which causes issues as not all transformations can translate into css/html. If those components could be set to export as a flat image all those issues would be solved. Any way to do this currently or is it planned for future release?
I can’t seem to find a way to turn off the red measurement tool. If I go to View > Hide UI it does remove it, but it also removes other side navigation components that I need available.
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.
