Skip to content

Administration: Fix misaligned spinner in admin screens#11649

Open
t-hamano wants to merge 3 commits intoWordPress:trunkfrom
t-hamano:65131-spinner-position
Open

Administration: Fix misaligned spinner in admin screens#11649
t-hamano wants to merge 3 commits intoWordPress:trunkfrom
t-hamano:65131-spinner-position

Conversation

@t-hamano
Copy link
Copy Markdown
Contributor

Trac ticket: <!-- insert a link to the WordPress Trac ticket here -->

How to Test

Register the following code as a browser bookmark. This will make it easier to test by visualizing the .spinner element.

javascript:(()=>{document.querySelectorAll('.spinner').forEach(e=>e.style.visibility='visible')})();

Screenshots

Classic Editor > Publish Sidebar > Update or Publish button

image

Classic Widget Editor > Save button

image

Posts > Tags > Add Tag button

image

Menus > Add to Menu button

image

Customize > Menus > Menu > Add Items > Custom Links > Add to Menu

image

Media (List view) > Edit > Edit Image button

image

Media (List view) > Edit > Update button

image

Media (List view) > Attach > Search input field

image

Theme File Editor > Update File button

image

Plugin File Editor > Update File button

image

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.

Adjust the default `.spinner` top margin so it aligns with adjacent buttons, and remove the now-redundant offset on `#publishing-action .spinner`. Add `vertical-align: top` to the spinner inside `#template .submit` so it lines up correctly with the surrounding submit controls.

Fixes #65131.
The default `.spinner` top margin was increased to align spinners with adjacent buttons across admin screens, but that offset misaligns the spinner inside Customizer accordion triggers. Override it back to `0` in this context so the spinner remains vertically centered with the trigger label.

Follow-up to [previous commit on this branch].

See #65131.
width: 20px;
height: 20px;
margin: 4px 10px 0;
margin: 10px 10px 0;
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change changes the default top margin for all spinners, so we need to be aware. We need to verify in various places that this does not cause unintended shifts.

Comment on lines +575 to +577
.accordion-section-title button.accordion-trigger .spinner {
margin-top: 0;
}
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Without this change, the spinner position in Customizer > Menus > Accordion Title will be misaligned.

Image

@t-hamano t-hamano marked this pull request as ready for review April 27, 2026 04:20
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 27, 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 wildworks, shailu25.

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

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

@shail-mehta
Copy link
Copy Markdown
Member

Spinners Alignment Issue is Resolved ✅

Classic Editor Add / Edit Post:

Before After
before-patch after-patch

Classic Widget Editor: Save Button:

Before After
before-patch after-patch

Add Tag Button:

Before After
before-patch after-patch

Add Menu Item:

Before After
before-patch after-patch

Customizer: Add Custom Link Menu Item:

Before After
before-patch after-patch

Media: Edit Image button

Before After
before-patch after-patch

Media: Update button

Before After
before-patch after-patch

Theme File Editor - Update File button

Before After
before-patch after-patch

Plugin File Editor - Update File button

Before After
before-patch after-patch

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.

2 participants