Skip to content

Administration: Remove line-height from input elements.#11156

Closed
manishdhorepatil-art wants to merge 1 commit intoWordPress:trunkfrom
manishdhorepatil-art:64763-remove-input-line-height
Closed

Administration: Remove line-height from input elements.#11156
manishdhorepatil-art wants to merge 1 commit intoWordPress:trunkfrom
manishdhorepatil-art:64763-remove-input-line-height

Conversation

@manishdhorepatil-art
Copy link

Description

Removes the line-height: 2.71428571 declaration from standard admin input elements. Height remains 40px via min-height; only the line-height is removed.

Changes

  • File: src/wp-admin/css/forms.css
  • Removed one line-height line from the rule that targets input[type="datetime"] through input[type="week"] (and related types).

Testing

  • Checked inputs on Settings → General and other admin forms.
  • Confirmed input height unchanged (40px) and selection highlight no longer fills the full field.

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

Fixes #64763

Removing line-height keeps the 40px height via min-height and fixes
the text selection highlight extending to full field height.

Props wildworks, Risad212.
Fixes #64763.
@github-actions
Copy link

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

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @ManishDhorepatil.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

Core Committers: Use this line as a base for the props when committing in SVN:

Props huzaifaalmesbah, manishxdp.

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 4, 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.

@huzaifaalmesbah
Copy link
Member

huzaifaalmesbah commented Mar 4, 2026

Thanks for the PR.
I noticed there is already an older PR #11099 for the same issue and it has been reviewed by a committer. Maybe it would be better to continue contributing there instead of opening a new PR.

@manishdhorepatil-art
Copy link
Author

@huzaifaalmesbah Thanks for review. okay noted

@t-hamano
Copy link
Contributor

t-hamano commented Mar 4, 2026

I’m closing this PR to focus on #11099.

@t-hamano t-hamano closed this Mar 4, 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.

4 participants