#Google webfont in email code#

This would require a different solution and since we are able to edit the fonts in the editor itself, we will not be adding Google Font support in the Styles panel. We have a styles panel that is for global styles that has a completely different implementation.

Styles Panel Not Supported: This implementation is within the editor itself.

Otherwise, the font will fall back like mentioned above. If either of these fonts are selected, they will work. We have thousands of free web fonts to choose from, courtesy of Google Fonts. They do however natively support two fonts (Google designed fonts) Google Sans and Roboto. On the web we get a rich choice of typography options.

No support in Gmail: Gmail is a very popular email client and even though it is ironic, Google does not support their own web fonts.

This does not include all Google Web Fonts.

Not all fonts from Google Fonts are available: At this time there are 640+ fonts available within the editor.

The workaround is to search for a web font on the Google fonts site and then type the desired font name into the type ahead to select. That is, when selecting a web font from the dropdown, not all of the available fonts will be displayed.

Chrome Known Issue: dataList limited: There is a known issue with dataList that is specific to the Chrome browser.

If for any reason the web font that was selected is not supported in the email client of the recipient, there are two fonts that the text will fall back to, Roboto and Ariel. Select the closest matching google fonts to your intended styling, and make sure to set as many fonts that will need to be different.

#Google webfont in email code#

Fallback Fonts: Email clients all differ in their level of support for web fonts. As an example, if you want to set your email up to have Helvetica as its fallback instead of Arial, you can use the following code in your CSS: font-family.Net-Results Landing Page Builder Basics.

Using Non Net-Results Forms in Net-Results.