Report a Problem

Hello,I experience issues when exporting vector icons as SVG. When the exported icon position is a plain pixel, the export is correct, and has the same size as in the design file.The icon is at x= 0 ; y = 0This is the exported SVG file content:<svg width="1667" height="2500" viewBox="0 0 1667 2500" fill="none" xmlns="http://www.w3.org/2000/svg"><g clip-path="url(#clip0_20_4)"><path d="M416.833 2500C646.833 2500 833.5 2313.33 833.5 2083.33V1666.67H416.833C186.833 1666.67 0.166698 1853.33 0.166698 2083.33C0.166698 2313.33 186.833 2500 416.833 2500Z" fill="#0ACF83"/><path d="M0.166698 1250C0.166698 1020 186.833 833.333 416.833 833.333H833.5V1666.67H416.833C186.833 1666.67 0.166698 1480 0.166698 1250Z" fill="#A259FF"/><path d="M0.166698 416.66

ok so I've made this pink and red logo with lines shooting out of the sides, all in figma. I used masks to create the finished look. When I export as PNG it works, but when I export as SVG to add to illustrator it does not work and instead the lines don't show up and only the mask show's, here is a screenshot of what I mean in illustratorwhen I try flattening the image the lines become black and the mask section fills out in that reddish color, which is definitively not what I'm trying to accomplishAny help would be greatly appreciatedthis is what I see in illustratorthis is when I flatten the image, which is totally not what I want

How can I make it so components can have a boolean “visibility” property without this? 

Figma file cover takes too long to sync up with the latest change from file. This issue has been being for along time and should to be resolved before the Cover size update

I am facing a bug where Figma does not correctly reference variables in a different collection even when the appropriate modes are set. For context, I have created a simple multi-brand design system with: Primitives collection: storing hex values of colors for each of my company’s brands (yellow and green) Semantic collection: storing references to variables in the primitive collection for the same brands After setting up the primitives collection, when I try and edit the variable for green brand in the semantic collection, the variable ‘picker’ window shows the correct green that should be referenced from primitives, however for some reason this does not apply.  The video demonstrates the issue. I also show correctly applying the mode for the page to be the green brand from primitives when attempting to troubleshoot.  Happy to hear if

Asset search recognizes PascalCase within the file where the component is defined but fails to do so when searching from a different file.For example, if I search for “can” within the file containing the TrashCan component, it appears in the results. However, searching for “can” from another file does not return TrashCan—only searching for “trash” works. This seems like a bug.  

Haven’t been able to find anyone else experiencing this so apologies if it’s already documented, but I’m getting a really annoying bug when selecting the trigger for a prototype where no matter where I am on the page it cuts off the options dialogue. Is there a fix?   

Hello everyone, I have a problem with a component and the ignore auto layout command.I have constructed a component of two elements, a circle and a group, the latter consisting of two circles. I have a problem when I resize the component. When I resize the component the red circle changes size, but the spinner (where the ‘ignore auto layout’ is applied) remains the same fixed size, despite the fact that the component has the constraints set to left/right and high/low.If I detach the component, it works fine.If I modify the component within the component set, it works fine.I need to use the component with these two constraints because I use a system with variable collections and without this, if I change the dimensions, the whole system explodes.

When i add the “ignore auto layout” in a parto of component, this doesn’t work. If i detach the same component it works correctly. 

0: {name: 'color/Brand/Alpha/Primary', id: 'VariableID:1:18'} 1: {name: 'color/Brand/Alpha/Secondary', id: 'VariableID:1:3'} 2: {name: 'color/Brand/Primary', id: 'VariableID:1:17'} 3: {name: 'color/Brand/Secondary', id: 'VariableID:1:5'} 4: {name: 'font/family/primary', id: 'VariableID:1:8'} 5: {name: 'font/weight/regular', id: 'VariableID:1:10'} 6: {name: 'font/weight/medium', id: 'VariableID:1:11'} 7: {name: 'mode/modes', id: 'VariableID:1:7'} <- resolvedType: String 8: {name: 'font/family/secondary', id: 'VariableID:1:9'} 9: {name: 'font/line height/string', id: 'VariableID:3:2'} Hey everyone, This is what’s returned by getLocalVariableCollectionsAsync().variables, and as you can see, the order isn’t correct. For instance, variables inside the font folder should be grouped together, and color/Brand/Primary & Secondary should appear before the nested folder color/Bra

I encountered an issue with the Alibaba PuHuiTi font in Figma. When I type the character "收", it appears as "护" instead. I have tried refreshing Figma, reinstalling the font, and testing it on different devices, but the issue persists.Could you help check if this is a known issue or provide any possible solutions?

Question:Hi Figma Community, I'm encountering an issue with my prototype. While everything appears correctly on the design canvas, some interactions or elements don't work when I preview it. Has anyone experienced this before, and could you offer any insights or solutions? Thanks!

When I select a light color, ie any of the second line, the connector will use the color at the first line, you can even see the selected is the one I chose but the connector will still use the darker color. It also happened when I tried to copy a color from other element, it won’t respect the color I chose. 

Support team, I got error.message to say I don't have permission to access prototypes I used previousely.  It was my projects for demonstrate to.my clients,.it gave very bad feeling and feedback from my client when I want to demo it.I used them couples week ago,.why I can't access them suddenly? https://www.figma.com/proto/aq63bRsBMq9Nv7a6ZijqcY/%E9%94%80%E5%94%AE%E5%9F%9F%E5%8F%AF%E8%A7%86%E5%8C%96%E7%9C%8B%E6%9D%BF?page-id=0%3A1&node-id=1066%3A17101&viewport=247%2C-203%2C0.04&scaling=scale-down-width&starting-point-node-id=1066%3A17101!-->!--> https://www.figma.com/proto/aq63bRsBMq9Nv7a6ZijqcY/%E9%94%80%

Here is a video demonstrating the trouble or bug. Responsive fonts are adapted during the smart animate transition. This disrupts the desired animation. Fonts using variables should be cached in hidden states. Locking the mode to MD for the cards when the entire screen is on mode LG works… but then my composition is fake because it’s not the good font sizes !

Just updated my desktop app to and am getting runtime errors pretty consistently on plugins I’ve built that were previously running fine. Here’s the console error:jsvm-cpp.wasm.br:0x23113 Uncaught (in promise) RuntimeError: memory access out of bounds    at jsvm-cpp.wasm.br:0x23113    at jsvm-cpp.wasm.br:0x3a412    at jsvm-cpp.wasm.br:0x26724    at jsvm-cpp.wasm.br:0x33106    at jsvm-cpp.wasm.br:0x2c352    at jsvm-cpp.wasm.br:0x2bab3    at jsvm-cpp.wasm.br:0x11f6    at jsvm-cpp.wasm.br:0x6188    at 2430-23a15bad9b36a906.min.js.br:797:87469Once I start seeing this error, the plugin refuses to open until I restart the app. After it restarts, I can open the app a few times before the error starts back up again.The issue seems to be with loading fonts. If I remove all the font code, the plugin opens without complaint. Something has changed in the latest update that seems to be causing this

Hovers on interactive components are malfunctioning in the prototype and present modes in a few different ways: Rendering text oddly, letters are getting jumbled Filling in areas with color Seemingly disappearing from view Seeing this on 2021-04-07T23:50:00Z

My Figma isn’t suggesting replacements for misspelled words. It does highlight the spelling errors, but when I Command-click or Control/Option-click, no alternative spellings are offered.I want Figma to flag errors and provide replacement suggestions, as I’ve seen this working for my colleagues.I’ve checked that my language is set to UK English under Figma > Text > Spell Check, restarted Figma, and I’m using the native desktop version on a Mac (not the web app).Any advice on how to fix this? I’m dyslexic and working on shared FigJam boards with my colleagues and not being able to correct my terrible spelling is inhibiting and painful 

When switching variable modes in an overlay the new values do not follow the autolayout rules. I think this is a bug because closing and reopening the model will fix the autolayout issues. To fix this I included a duplicate of the modal and switch between them when changing the variable mode. Let me know if anyone is interested in links or images.

Is it possible to customize figma so that when I click anywhere in the component, I get to the parent layer and get in the right panel all the settings of my component?Since now when I click anywhere in the component its child layer is highlighted.Now for this I had to write a plugin that when I select a child layer redirects me to the parent layer + breaks all the nesting. But the plugin takes up space on the workspace and it is not very convenient to run it all the time. It would be cool to be able to do hockey in the settings.For example, pressing the default Commant + Clik I get to the selected layer, but for example, when pressing Option + Commant + Click that I would get to the parent layer of the component while the component itself remained swallowed upCommand + Click go to selected layer

When exporting a frame to PNG, Figma is increasing the image size by 1 pixel only on the horizontal axis, which is a problem when I need artwork with exact dimensions.  

Hey! I found peculiar issue with size variable with constrained proportions in Figma. When adjusting size values with variables, I expected both variables to update simultaneously since constraints was on, but it didn’t change the opposite value at all.

Whenever I create or open a Figma file with the new UI in Firefox (currently v128.0.3) on Mac, I can only see half the canvas. Not very helpful…

I have found some of my responsive designs when viewed as a responsive prototype are scaling down correctly but then are still scrollable to the right with a blank area. Solution - Set the Scroll Behaviour Overflow to Vertical on the top most frame (not sure if this works if your top most frame is a component) Hope this helps someone, Cheers

Hi guys, Is this a bug or is it a missing feature? If I take a components from one file, and I use it in another file, and after using it it the second file I make some changes in the original component, the changes won’t reflect in the second file. I basically need to copy it again from the main file to the second file.