Skip to content

[Backport to release/10.6] Fix styling issues with WordPress 7.0#63825

Merged
jorgeatorres merged 1 commit intorelease/10.6from
cherry-pick-PR63779-to-release/10.6
Mar 24, 2026
Merged

[Backport to release/10.6] Fix styling issues with WordPress 7.0#63825
jorgeatorres merged 1 commit intorelease/10.6from
cherry-pick-PR63779-to-release/10.6

Conversation

@woocommercebot
Copy link
Copy Markdown
Collaborator

This PR is a cherry-pick of #63779 to release/10.6.

Original PR Description

Changes proposed in this Pull Request:

  • Updates various CSS rules to prevent the admin dashboard displaying incorrectly in WordPress 7.0
  • The changes are conditionally applied if WP >= 7.0
  • Inline comments explain each rule change.

Closes WOOPLUG-6412
Closes WOOPLUG-6442

Screenshots or screen recordings:

Order list

Before After 6.9
image image image

Individual Order

Before After 6.9
image image image

Individual order refund

Before After 6.9
image image image

Individual Product publish metabox

Before After 6.9
image image image

Individual product details

Before After 6.9
image image image
Before After 6.9
image image image
Before After 6.9
image image image

Coupons

Before After 6.9
image image image

Settings

Before After 6.9
image image image

How to test the changes in this Pull Request:

Using the WooCommerce Testing Instructions Guide, include your detailed testing instructions:

  1. Set your store up to use WordPress 7.0 (beta5)
  2. Visit each of the sections screenshotted above, and ensure they display correctly, no poorly sized controls, nothing out of alignment etc.
  3. Look for visual inconsistencies across any admin surface, compared to when viewed WordPress 6.9
  4. Downgrade to WordPress 6.9
  5. Ensure the styling of these admin surfaces looks the same as it did before these changes
  6. Click around the admin and ensure nothing looks out of place, general smoke testing of your team's areas of responsibility would be good.

Testing that has already taken place:

Milestone

Note: Check the box above to have the milestone automatically assigned when merged.
Alternatively (e.g. for point releases), manually assign the appropriate milestone.

Changelog entry

  • Automatically create a changelog entry from the details below.
  • This Pull Request does not require a changelog entry. (Comment required below)
Changelog Entry Details

Significance

  • Patch
  • Minor
  • Major

Type

  • Fix - Fixes an existing bug
  • Add - Adds functionality
  • Update - Update existing functionality
  • Dev - Development related task
  • Tweak - A minor adjustment to the codebase
  • Performance - Address performance issues
  • Enhancement - Improvement to existing functionality

Message

Changelog Entry Comment

Comment

@github-actions github-actions bot added this to the 10.6.0 milestone Mar 24, 2026
@github-actions github-actions bot added the plugin: woocommerce Issues related to the WooCommerce Core plugin. label Mar 24, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Testing Guidelines

Hi @jorgeatorres @opr ,

Apart from reviewing the code changes, please make sure to review the testing instructions (Guide) and verify that relevant tests (E2E, Unit, Integration, etc.) have been added or updated as needed.

Reminder: PR reviewers are required to document testing performed. This includes:

  • 🖼️ Screenshots or screen recordings.
  • 📝 List of functionality tested / steps followed.
  • 🌐 Site details (environment attributes such as hosting type, plugins, theme, store size, store age, and relevant settings).
  • 🔍 Any analysis performed, such as assessing potential impacts on environment attributes and other plugins, conducting performance profiling, or using LLM/AI-based analysis.

⚠️ Within the testing details you provide, please ensure that no sensitive information (such as API keys, passwords, user data, etc.) is included in this public issue.

@github-actions
Copy link
Copy Markdown
Contributor

Test using WordPress Playground

The changes in this pull request can be previewed and tested using a WordPress Playground instance.
WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Test this pull request with WordPress Playground.

Note that this URL is valid for 30 days from when this comment was last updated. You can update it by closing/reopening the PR or pushing a new commit.

@github-actions
Copy link
Copy Markdown
Contributor

Size Change: +1 kB (+0.02%)

Total Size: 5.97 MB

Filename Size Change
./plugins/woocommerce/client/legacy/build/css/admin-rtl.css 39.3 kB +503 B (+1.3%)
./plugins/woocommerce/client/legacy/build/css/admin.css 39.3 kB +502 B (+1.29%)

compressed-size-action

@jorgeatorres jorgeatorres enabled auto-merge (squash) March 24, 2026 10:25
@jorgeatorres jorgeatorres merged commit f1c9be6 into release/10.6 Mar 24, 2026
60 of 62 checks passed
@jorgeatorres jorgeatorres deleted the cherry-pick-PR63779-to-release/10.6 branch March 24, 2026 10:25
@github-actions github-actions bot added the metric: feature freeze exception A tracking label for PRs that were merged after the feature freeze. label Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

metric: feature freeze exception A tracking label for PRs that were merged after the feature freeze. plugin: woocommerce Issues related to the WooCommerce Core plugin.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants