Older Classic Themes - Font family not reflected in editor #6999
Description
Quick summary
On certain older classic themes, the font family is not displayed in the editor, though it does appear on the live site.
Themes presenting this issue:
- Libretto
- Independent Publisher 2
- Cerauno
- Twenty Eleven
I haven't been able to identify a pattern to the themes where this shows up, but see bottom of report for further testing notes.
Steps to reproduce
- On a Simple or AT site, activate one of the themes listed above
- In a new page or post, add text in a paragraph block.
- Enable Paragraph block > Block Settings > Typography > Font Family
- Change the font family selection
What you expected to happen
The font in the editor to change to reflect the selected font family, or default font family.
What actually happened
No change occurs.
Deactivating Editor > Preferences > Use Themes Styles reverts the font to a larger typescale, making it easier to read, but does not workaround the issue.
Screen.Capture.on.2023-04-05.at.11-08-12.mp4
The Live Site still displays the default font:
Impact
Some (< 50%)
Available workarounds?
No but the platform is still usable
Platform (Simple and/or Atomic)
Simple, Atomic
Logs or notes
Tested on Simple and Atomic sites using WP v6.2, Gutenberg 15.4.0
-
On WPcom Simple and AT sites, this issue presented on the following tested themes:
- Libretto
- Independent Publisher 2
- Cerauno
- Twenty Eleven
-
On the same Simple and AT sites, the following themes did not present the issue:
- Yuga (FSE)
- Twenty Fifteen
- Twenty Twenty
- Twenty Twenty-One
-
On a Pressable site not connected to WordPress.com, Libretto did not present the issue in either Gutenberg 15.4.0 or 15.5.0. Other tested themes like Twenty Eleven WordPress.com and Cerauno don't have a Font Family selection in the block settings.
Screen.Capture.on.2023-04-05.at.11-24-27.mov
Originally this issue had been reopened: Automattic/wp-calypso#57043 however based on my testing, this does not look like a full regression of that issue.
This is another older (closed) issue that might inform what's happening here: #3280