It took me some time to be able to test this :). Should we include a variation with a font file in the "emptytheme" embedded in the Gutenberg plugin to make testing this easier in the future?

Regardless, I'm noticing two bugs:

I have a default theme.json without font family (default) and one variation with a font applied to the whole body.

• If apply the variation on the editor and save, then reload the frontend, the frontend is still displaying the default font family.
• In the editor, if I have the variation applied and I save and reload. I'm not able to "reset" the styles to the default theme.json. Basically when I click "reset styles", the variation's font family is still applied somehow.

(Testing in safari)

This emptytheme PR works for testing: WordPress/theme-experiments#304

I'm also testing alongside the Twenty Twenty-Two style variations here: WordPress/wordpress-develop#2440

The former works just fine aside from the issues that @youknowriad noted above — I am able to reproduce those. But the Twenty Twenty-Two PR doesn't seem to load any fonts at all. 🤔

If someone could help gut check that for me, I'd appreciate it — I'm unclear if the problem is over on the Twenty Twenty-Two end or in this PR.

If apply the variation on the editor and save, then reload the frontend, the frontend is still displaying the default font family.

Apparently I didn't test after rebasing the PR, and some things have changed 😅
Fixed. It appears that after some recent changes in the webfonts API, now an extra call is required to enqueue the webfont, registering them is not enough.

In the editor, if I have the variation applied and I save and reload. I'm not able to "reset" the styles to the default theme.json. Basically when I click "reset styles", the variation's font family is still applied somehow.

After some debugging, I don't think this is a bug in this PR...
The problem here is that the theme.json file in the emptytheme doesn't have a default typography defined, while the variation does.
If in theme.json I add this (see snippet below) then everything works:

	"styles": {
		"typography": {
			"fontFamily": "sans-serif"
		}
	}

If we want to change that behavior, it will need to be done in a separate PR since it's more generic and not related to the webfonts... it's an overrides/resets issue when a variation has something defined that doesn't exist in the main file.