MailPoet currently treats font loading for both subscription forms and emails in the same way, despite the fact that browsers and email clients deal with fonts differently. MailPoet currently loads a restricted subset of fonts for use in both scenarios.
It is not logical to restrict the fonts available for subscription forms in a web browser to the very limited number of fonts deemed safe for an email client. These are different technologies, with different use cases. Where custom Google fonts have been used on a website, this creates visual inconsistency between the MailPoet form and the rest of the website - for absolutely no practical reason.
MailPoet, as a block-based plugin, should respect the font choices made by the website owner/designer, and present any theme-enabled/locally loaded fonts as frontend options, as other block-based plugins do.
Thanks in advance for consideration.