Skip to content

Modify active theme colors to fix empty div background#11121

Open
joedolson wants to merge 1 commit intoWordPress:trunkfrom
joedolson:64720-Fix-theme-browser-empty-div-appearance
Open

Modify active theme colors to fix empty div background#11121
joedolson wants to merge 1 commit intoWordPress:trunkfrom
joedolson:64720-Fix-theme-browser-empty-div-appearance

Conversation

@joedolson
Copy link
Contributor

Changes the active theme actions panel to have no background color to avoid possibility of empty background.

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

Use of AI Tools


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.

Changes the active theme actions panel to have no background color to avoid possibility of empty background.
@github-actions
Copy link

github-actions bot commented Mar 3, 2026

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

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

@joedolson
Copy link
Contributor Author

After change:

Screenshot 2026-03-02 at 6 33 45 PM

With customizer disabled:

Screenshot 2026-03-02 at 6 38 49 PM

Before, with customizer enabled:

Screenshot 2026-03-02 at 6 39 43 PM

@joedolson joedolson requested a review from fabiankaegy March 3, 2026 00:40
@github-actions
Copy link

github-actions bot commented Mar 3, 2026

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.

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