Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions src/wp-admin/css/edit.css
Original file line number Diff line number Diff line change
Expand Up @@ -706,12 +706,19 @@ form#tags-filter {
font-weight: 600;
}

#post-status-select,
#post-visibility-select,
#comment-status-radio {
line-height: 1.5;
margin-top: 3px;
}

#post-status-select select {
display: block;
margin-bottom: 0.7em;
width: 100%;
}
Comment on lines +716 to +720

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I agree with this change since that way the buttons don't really shift depending on the width of the selected value. This is even more relevant on languages where those strings are longer.

But it seems like max-width is not necessary?

Suggested change
#post-status-select select {
max-width: 100%;
width: 100%;
}
#post-status-select select {
width: 100%;
}

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Good point. I removed max-width. I kept display: block and margin-bottom so the OK/Cancel controls sit below the full-width select without requiring a markup wrapper.


#linksubmitdiv .inside, /* Old Link Manager back-compat. */
#poststuff #submitdiv .inside {
margin: 0;
Expand Down
Loading