Skip to content

Set inline edit input fields to use compact size#11117

Open
joedolson wants to merge 11 commits intoWordPress:trunkfrom
joedolson:Update-bulk-edit-input-height-64685
Open

Set inline edit input fields to use compact size#11117
joedolson wants to merge 11 commits intoWordPress:trunkfrom
joedolson:Update-bulk-edit-input-height-64685

Conversation

@joedolson
Copy link
Contributor

Uses compact input sizes for all text & select inputs in inline editing.

Effects both quick edit and bulk edit.

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

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.

@github-actions
Copy link

github-actions bot commented Mar 2, 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, sabernhardt, 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

github-actions bot commented Mar 2, 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.

@joedolson
Copy link
Contributor Author

After patch:

Screenshot 2026-03-02 at 2 57 06 PM Screenshot 2026-03-02 at 2 54 32 PM

@joedolson
Copy link
Contributor Author

Before patch:
Screenshot 2026-03-02 at 2 58 42 PM

Screenshot 2026-03-02 at 2 58 26 PM

@joedolson
Copy link
Contributor Author

Noting there's still work to do on the date and password fields

@joedolson
Copy link
Contributor Author

Reverted the switches to flex layout. Would be nice, but there's actually a lot of work to get that working with some of the existing styles. Better to leave that for some future structural design changes, if they happen.

@joedolson
Copy link
Contributor Author

After patch, following revert:

Screenshot 2026-03-02 at 6 01 57 PM Screenshot 2026-03-02 at 6 01 40 PM

@joedolson
Copy link
Contributor Author

I didn't quite match the screenshot sizes; the alignment differences in the password and date fields in the new after are just artifacts of slightly different screen width.

@shail-mehta
Copy link
Member

shail-mehta commented Mar 3, 2026

Bulk Edit:

Before After
before-patch after-patch

@shail-mehta
Copy link
Member

Quick Edit:

Before After
before-patch after-patch

Copy link

@sabernhardt sabernhardt left a comment

Choose a reason for hiding this comment

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

I'm mostly concerned about the right padding on inputs, but I added more comments.

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.

3 participants