Skip to content

Admin reskin: Fix vertical alignment of pagination input in list tables.#11392

Closed
rbcorrales wants to merge 1 commit intoWordPress:trunkfrom
rbcorrales:fix/64975-pagination-alignment
Closed

Admin reskin: Fix vertical alignment of pagination input in list tables.#11392
rbcorrales wants to merge 1 commit intoWordPress:trunkfrom
rbcorrales:fix/64975-pagination-alignment

Conversation

@rbcorrales
Copy link
Copy Markdown

The page number input in WP_List_Table pagination was vertically misaligned with the navigation buttons due to different baseline positions.

The fix adds vertical-align: top to .current-page, which aligns the input flush with the buttons without side effects on the bottom pagination row (which has no input field).

Before:
image

After:
image

For additional context, other approaches explored and discarded:

  • display: flex + align-items: center on the pagination containers fixed alignment but changed horizontal spacing and affected the bottom pagination row.
  • vertical-align: middle on buttons and text elements fixed the top row but shifted the bottom pagination which was already aligned.

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

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 4.6
Used for: Measuring computed styles in the browser and code reviewing. Final fix validated and reviewed by me.

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

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.

@github-actions
Copy link
Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.

SVN changeset: 62182
GitHub commit: a6d9020

This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.

@github-actions github-actions bot closed this Mar 30, 2026
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