Missing variable font values ("font-variation-settings") over plugin/rest api

Hi @MKitPlug, Thank you for sharing your thoughts on this!

While we await input from our community, I’ll check internally to see if we have any additional information on this. We will update you once further information is available.

Also, I am unsure, but I came across a similar post at this link: Missing variable font values in style Please feel free to take a look!

Thank you for your input, and if anyone in our community has any insights, please feel free to vote or comment to support this idea!

Hello @MKitPlug, I’ve looked into this matter internally and unfortunately, it is not currently feasible.

However, we’re already aware of the demand for it. I have included your suggestion in our internal report to bring more attention to it.

Thank you again for your valuable input!

​@Junko3 I’d like to also note a certain nature of this demand: Without plugin API access, there are no workarounds at all other than manually selecting individual text nodes and modify values. This significantly limits a team’s ability to deploy variable fonts at scale reliably. You can’t do that manually with millions of frames.

Hello ​@Junko3 , 

Are there any news about possible developments in this regard? 

Have you found any workaround for this? ​@MKitPlug?

​@Junko3 We would highly appreciate any news here. We are also missing the lack of variables there….

​@Qinyi_Yao You can use styles to reduce manual effort at least by a bit, but you are still not able to sync design and code properly without api issue solved. 

What have you done meanwhile to cope with the situation?