wordpress-develop icon indicating copy to clipboard operation
wordpress-develop copied to clipboard

Add `wp-theme-<name>` and `wp-child-theme-<name>` classes to body tag

Open nirajgiriXD opened this issue 1 year ago • 2 comments

Description

This PR introduces new classes to the body tag in WordPress themes. The classes wp-theme-<name> and wp-child-theme-<name> (if child theme) are added, where <name> represents the sanitized name of the active theme and child theme, respectively.

Changes Made

  • Added wp-theme-<name> class to the body tag for the current theme.
  • Added wp-child-theme-<name> class to the body tag for the current theme (if child theme).

Screenshots

  • For twentytwentyfour theme
theme
  • For a child theme named childtheme having twentytwentyfour as parent theme
child-theme

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

nirajgiriXD avatar Jul 16 '24 10:07 nirajgiriXD

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.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @[email protected], @jonnynews.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

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

Props nirajgirixd, poena.

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

github-actions[bot] avatar Jul 16 '24 10:07 github-actions[bot]

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.

github-actions[bot] avatar Jul 16 '24 10:07 github-actions[bot]

If these class names are intended to help plugins with theme specific styles, they also need to be present in the Site Editor. (They are already available in the Customizer preview)

carolinan avatar Dec 03 '24 06:12 carolinan

I checked again, neither of the existing body classes are added in the Site Editor. I am not sure why. It should be treated as a separate issue and not block this update.

carolinan avatar Jan 03 '25 06:01 carolinan

A commit was made that fixes the Trac ticket referenced in the description of this pull request.

SVN changeset: 59698 GitHub commit: https://github.com/WordPress/wordpress-develop/commit/0f6707de3023234b85e7186fa5cd10ad039d0109

This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.

github-actions[bot] avatar Jan 24 '25 10:01 github-actions[bot]