[CanoV2]

Description

This PR addresses an additional font-size inconsistency in the Search block when using the Twenty Twenty theme.

The Search block label uses a 21px font size in the editor, but a 16px font size on the front end at the tested desktop viewport.

This change adds font-size: inherit to .entry-content .wp-block-search__label, allowing the label to inherit the font size from its parent container.

Testing

• Activated the Twenty Twenty theme.
• Added a Search block to a page.
• Compared the label font size in the editor and on the front end.
• Confirmed that the label uses 21px in both views after applying the change.

This complements the existing font-family fix proposed in PR #7877.

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

Use of AI Tools

AI assistance: Yes
Tool(s): ChatGPT
Model(s): GPT-6
Used for: CSS investigation and code suggestions. The change was manually tested.

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

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

Props agusz23.

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

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.

[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

• 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.