Same issue here! Surprised that this has not been solved yet.
Wow, one year after that and I have the same issue here!
I am facing the same issue. I have raised a ticket for the bug. Explained all the details. I am also a font engineer, would love if Figma fixes this issue. Browsing this thread, it looks like Figma is not giving it enough attention.
Figma developers, you can reach out to me if you need any assistance. It is a simple fix, there is a particular property for font-weight in the font data file. Figma is not reading it correctly.
Agree that this is a huge problem. One of the selling points of using Figma is smooth developer handoffs without needing to use an additional add on product or tool (i.e. InVision, Zepelin). This bug is creating unnecessary friction in the development process and needs to be remedied. This particular bug is causing me to reconsider the set of tools my team is using - we need to have smooth handoffs with our development team - it’s better for productivity, morale, and our cross functional team relationships not to mention meeting launch deadlines.
Same issue here! Would like to see this bug fixed.
We had this same issue using an Adobe font, and installing it locally into our font books “solved” the issue. So, it seems like one workaround is to have developers all install the font on their machines. Free webfonts do not seem to suffer from this problem (Inter is handled correctly for us, for example).
Also having the same issue where while using the desktop app on Mac, the font Gotham, Medium shows as
font-weight: 400 in the Inspect panel.
The font is installed locally, so that has not solved the problem as it has for some others. I really hope this is a high priority bug to fix, b/c this adds way too much friction to the handoff process. We also do not have the resources to just buy Editor seats for all our devs—a major selling point for Figma was that it supposedly allowed for better collaboration without needing to do that. 👀
Upvote, this and does anyone know if there is a bug out there to fix this? This is causing issues for my UI devs.
Upvote! This is causing unnecessary friction in our team.
Likewise, same problem here.
Having the same bug as well — has created a huge headache and now our team is questioning if there are values elsewhere that could have discrepancies.
Would really love to know when this is planned to be resolved. Really inconvenient and causes a lot of miscommunications.
Same issue Here. When will this issue be fixed?
Same issue Here. When will this issue be fixed?
It’s over 1 year and more. I think this is a serious issue.
WHY IS FIGMA DIDNT FIX THIS STILL NOW?
Same issue, not working properly even with the latest update ☹
Can’t believe that this issue is still not fixed yet for close to 2 years!!! how long does this actually take to fix? If I were figma I’d jump on this right away, as this bug causes much more pain than the joy those figjams bring
I have the same problem. Maybe Adobe fix this issue…
Still nothing new about this?
You should asap remove wrong specification items out of the Inspect panel, so it does not bring confusion to the developers!
Bump. This has been a pain in our handover process for a while and only now I’ve understood the root of the cause. This needs to be fixed.
Bump… please fix this Figma or give us the ability to declare font-weight overrides for the Inspect Panel
+1
this issue is causing handoff delays and misreporting of bugs in our team. is the solution in the works? it’s been consistently reported for almost two years now…
