Ensure Consistent Font Family for Excerpt and Full Post in Latest Posts Block (Editor)

[im3dabasia]

Trac ticket: https://core.trac.wordpress.org/ticket/62242

The font-family for the "Latest Post" block was previously inconsistent between the excerpt and full post in the editor. This change ensures the font-family remains the same when switching between excerpt and full post in the editor.

Changes made:
Added font-family: inherit; to .wp-block-latest-posts__post-full-content p to ensure font consistency in the editor.
This resolves the issue where the font family for the full post in the editor was different from the excerpt, ensuring consistency in the editing experience.

Before: (The full post content is having an inconsistent font family as compared to the excerpt in editor, excerpt in the frontend and, full content in the frontend)
After: (After the change the full content is consistent in the editor and the frontend just like how the excerpt is)

Before:

Screen.Recording.2024-11-18.at.4.45.56.PM.mov

After:

Screen.Recording.2024-11-18.at.4.45.08.PM.mov

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props im3dabasia1.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• The Plugin and Theme Directories cannot be accessed within Playground.
• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.