Make WordPress Core

Opened 7 weeks ago

Last modified 2 weeks ago

#64689 new defect (bug)

Customizer “Publish” button size appears larger in 7.0 compared to 6.9.1

Reported by: mohitbsf's profile mohitbsf Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: trunk
Component: Customize Keywords: close admin-reskin
Focuses: css Cc:

Description

WordPress versions compared:

6.9.1

7.0

Environment: Clean install, classic theme, no active plugins

Steps to Reproduce

Go to Appearance → Customize

Make any change so the Publish button becomes active

Compare the Publish button in WordPress 6.9.1 and 7.0

Expected Result

The Publish button should maintain consistent height, padding, and visual weight across versions unless intentionally updated as part of a UI refresh.

Actual Result

In WordPress 7.0, the Publish button appears:

Slightly taller

Visually heavier

Larger compared to its appearance in 6.9.1

This changes the visual balance of the Customizer header.

Additional Notes

Reproducible on clean installs

No custom admin styles

Reporting to confirm whether this change was intentional

Attachments (2)

Screen Shot 2026-02-21 at 01.29.42.png (115.8 KB) - added by mohitbsf 7 weeks ago.
32px-height-button.png (16.0 KB) - added by wildworks 6 weeks ago.
32px height button in Customizer header

Download all attachments as: .zip

Change History (10)

#1 @joedolson
7 weeks ago

  • Keywords close admin-reskin added
  • Version set to trunk

All buttons were enlarged intentionally, so I think this is intentional.

Pinging @fabiankaegy to confirm; I don't see a problem here, however.

#2 @mohitbsf
7 weeks ago

IMO. with all due respect, I think the publish button size should be same as before, as the current one looks like an unfinished job, I totally understand that it can be intentionally done, but revisiting this will be best.

#3 @audrasjb
7 weeks ago

This doesn't look like buggy to me.

#4 @mohitbsf
7 weeks ago

It's absolutely okay @audrasjb , but if we can consider, that will be best.

That's the only reason I have added this note in the end : Reporting to confirm whether this change was intentional

Team can take further decision on this, but if you see me as the end user after using WordPress for almost 8 years, I will always find that big Publish button as buggy or an unfinished job.

#5 @wildworks
6 weeks ago

It seems like the issue isn't with the size of the publish button itself, but rather with the lack of space above and below the button.

Here, I think a compact size seems more appropriate, i.e. 32px instead of 40px. The default button height has been increased from 30px to 40px, which may be too large in some contexts.

diff --git a/src/wp-admin/css/customize-controls.css b/src/wp-admin/css/customize-controls.css
index 3c0d40585c..6a0b1a6328 100644
--- a/src/wp-admin/css/customize-controls.css
+++ b/src/wp-admin/css/customize-controls.css
@@ -70,7 +70,7 @@ body {
 
 #customize-save-button-wrapper {
        float: right;
-       margin-top: 3px; /* Vertically center 40px button in 45px header */
+       margin-top: 7px; /* Vertically center 32px button in 45px header */
 }
 
 body:not(.ready) #customize-save-button-wrapper .save {
diff --git a/src/wp-admin/customize.php b/src/wp-admin/customize.php
index 2065e55ffb..d5d517cccc 100644
--- a/src/wp-admin/customize.php
+++ b/src/wp-admin/customize.php
@@ -198,13 +198,13 @@ do_action( 'customize_controls_head' );
                        <?php if ( $compatible_wp && $compatible_php ) : ?>
                                <?php $save_text = $wp_customize->is_theme_active() ? __( 'Publish' ) : __( 'Activate &amp; Publish' ); ?>
                                <div id="customize-save-button-wrapper" class="customize-save-button-wrapper" >
-                                       <?php submit_button( $save_text, 'primary save', 'save', false ); ?>
-                                       <button id="publish-settings" class="publish-settings button-primary button dashicons dashicons-admin-generic" aria-label="<?php esc_attr_e( 'Publish Settings' ); ?>" aria-expanded="false" disabled></button>
+                                       <?php submit_button( $save_text, 'primary save button-compact', 'save', false ); ?>
+                                       <button id="publish-settings" class="publish-settings button-primary button button-compact dashicons dashicons-admin-generic" aria-label="<?php esc_attr_e( 'Publish Settings' ); ?>" aria-expanded="false" disabled></button>
                                </div>
                        <?php else : ?>
                                <?php $save_text = _x( 'Cannot Activate', 'theme' ); ?>
                                <div id="customize-save-button-wrapper" class="customize-save-button-wrapper disabled" >
-                                       <button class="button button-primary disabled" aria-label="<?php esc_attr_e( 'Publish Se
ttings' ); ?>" aria-expanded="false" disabled><?php echo $save_text; ?></button>
+                                       <button class="button button-primary button-compact disabled" aria-label="<?php esc_attr
_e( 'Publish Settings' ); ?>" aria-expanded="false" disabled><?php echo $save_text; ?></button>
                                </div>
                        <?php endif; ?>
                        <span class="spinner"></span>

@wildworks
6 weeks ago

32px height button in Customizer header

#6 @huzaifaalmesbah
5 weeks ago

I agree that using a 32px compact button here makes sense. The default 40px button feels a bit large for the Customizer header, and the compact size provides better visual balance.

This ticket was mentioned in PR #11389 on WordPress/wordpress-develop by @wildworks.


2 weeks ago
#7

  • Keywords has-patch added

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

## Use of AI Tools

None

#8 @wildworks
2 weeks ago

  • Keywords has-patch removed

32px height button in Customizer header

I implemented this approach in https://github.com/WordPress/wordpress-develop/pull/11389

Note: See TracTickets for help on using tickets.