Skip to content

Editor: Restore the default editor styles for classic themes. - #16118

Open
mukeshpanchal27 wants to merge 1 commit into
WordPress:trunkfrom
mukeshpanchal27:fix/default-editor-styles
Open

mukeshpanchal27 wants to merge 1 commit into
WordPress:trunkfrom
mukeshpanchal27:fix/default-editor-styles

Conversation

@mukeshpanchal27

@mukeshpanchal27 mukeshpanchal27 commented Nov 20, 2026 •

Copy link
Copy Markdown
Member

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

Use of AI tools

I used Claude Code to find the regression, write the change and test, and draft this description. I reviewed the result.

🤖 Generated with Claude Code

`get_default_block_editor_settings()` read the default editor styles from `wp-includes/css/dist/block-editor/default-editor-styles.css`. The block editor package no longer ships that file, and [65716] deletes it during upgrades. Because of this, the `defaultEditorStyles` setting is always empty in 7.2. Classic themes without their own editor styles, and users who turn off "Use theme styles", lose the default font, font size, line height, block gap, and post title styles.

This moves the CSS from the last shipped version of that file into core, so the setting no longer depends on the file.

Follow-up to [65716].

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

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.

@mukeshpanchal27 mukeshpanchal27 self-assigned this Nov 20, 2026
@mukeshpanchal27
mukeshpanchal27 requested a balanced review from Copilot November 20, 2026 05:49
@mukeshpanchal27
mukeshpanchal27 marked this pull request as ready for review November 20, 2026 05:49
@github-actions

Copy link
Copy Markdown

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

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 or WordPress.org 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant