Skip to content

Classic Editor: reduce height of slug editing field#11551

Open
t-hamano wants to merge 1 commit intoWordPress:trunkfrom
t-hamano:65063-slug-field-height
Open

Classic Editor: reduce height of slug editing field#11551
t-hamano wants to merge 1 commit intoWordPress:trunkfrom
t-hamano:65063-slug-field-height

Conversation

@t-hamano
Copy link
Copy Markdown
Contributor

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

Use of AI Tools

None

Screenshots

Before After
image image

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 11, 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, sabernhardt, audrasjb.

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.

@t-hamano
Copy link
Copy Markdown
Contributor Author

Note that this PR contains minimal changes for 7.0. Ideally, we should refactor using the flex layout. Appropriate spacing should also be added, for example, like this.

1200px width:

image

700px width:

image

360px width:

image

@sabernhardt
Copy link
Copy Markdown

Consider changing the OK button from button-small to button-compact. It would have the same height as the input on smaller screens when combined with the buttons.css change in #11549.

Then the Cancel button might have a larger font size than 11px, too (by removing that rule).

@audrasjb
Copy link
Copy Markdown
Contributor

Honestly I would decrease the height of that specific input rather than increasing the height of the button. I know it would be an exception for that specific area but with the provided screenshots, we can see that there is a hierarchy issue: the permalink/slug area should not be displayed with the same visual hierarchy we have for the post title. The text in this section is smaller for this reason.

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