WordPress.org

Make WordPress Core

Opened 5 years ago

Last modified 5 months ago

#31261 new enhancement

Improve appearance of the slug field in the "Edit Post" page in the administration

Reported by: tyxla Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.0
Component: Posts, Post Types Keywords: has-patch
Focuses: ui, administration Cc:
PR Number:

Description

The slug field could use a couple of minor general improvements:

  1. The input has always been lacking a proper CSS width. Since there is nothing else in the slug meta box, the input can be extended to 100% width. I have observed the narrow slug field in as soon as version 3.0.
  2. The slug input horizontal/vertical centering within the meta box content div varies throughout the different versions. In 3.0, 4.1, and in trunk as well, there is more space at the bottom of the field, than at the top. Since the spacing on the sides is 12px, I suggest that the total top & bottom margin of the field within the slug box is also changed to 12px for consistency.

Attachments (1)

31261.patch (332 bytes) - added by tyxla 5 years ago.
Minor styling improvements to slug field - extending field to 100%, adding margin to properly center the field in the slug box.

Download all attachments as: .zip

Change History (4)

@tyxla
5 years ago

Minor styling improvements to slug field - extending field to 100%, adding margin to properly center the field in the slug box.

#1 @tyxla
5 years ago

  • Keywords has-patch added

#2 @helen
5 years ago

I'd rather get rid of that field/metabox, see #18523.

#3 @tyxla
5 years ago

As far as I understand, you are talking about removing the slug meta box in favor of the slug edit box in the Permalink section. This makes sense, but the Permalink section is not shown for non-public post types. So removing that meta box would prevent the user to manage the slug in non-public post types. And I've dealt with such cases in my experience - using non-public post types that are using the slug (and need a field to manage it). I'll post my opinion in #18523 for consideration.

Note: See TracTickets for help on using tickets.