Skip to content

Fix: Buttons output in extra_tablenav are too tall#11224

Closed
hbhalodia wants to merge 5 commits intoWordPress:trunkfrom
hbhalodia:fix/issue-64796
Closed

Fix: Buttons output in extra_tablenav are too tall#11224
hbhalodia wants to merge 5 commits intoWordPress:trunkfrom
hbhalodia:fix/issue-64796

Conversation

@hbhalodia
Copy link
Copy Markdown

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

Before (button does not placed inside .actions) After (button does not placed inside .actions)
Screenshot 2026-03-11 at 1 49 51 PM Screenshot 2026-03-11 at 1 46 33 PM

Use of AI Tools

  • None

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
Copy Markdown

github-actions bot commented Mar 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 hbhalodia, mukesh27, joedolson, nilambar, 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
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.

Copy link
Copy Markdown
Member

@mukeshpanchal27 mukeshpanchal27 left a comment

Choose a reason for hiding this comment

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

Thanks for the PR! Looks good to me.

@ernilambar
Copy link
Copy Markdown
Member

Before After
before-pr after-pr

@johnbillion johnbillion requested a review from fabiankaegy March 16, 2026 10:46
@shail-mehta
Copy link
Copy Markdown
Member

Buttons rendered within extra_tablenav are displaying correctly. ✅

Before After
before-patch after-patch

Copy link
Copy Markdown
Contributor

@joedolson joedolson left a comment

Choose a reason for hiding this comment

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

This fixes the specific named issue, but the same issue exists for other input types inserted in extra_tablenav, as well. E.g, adding a select or an input will also have the extra height.

I think the same logic should be used to ensure that other controls used by core in that context get the compact sizing. The select styling right above can be split between sizing characteristics & positioning characteristics.

I'm not sure that core uses an input in extra_tablenav anywhere, and it's more reasonable that extenders would need to style things not used by core, so it may not be necessary to add that.

@hbhalodia
Copy link
Copy Markdown
Author

This fixes the specific named issue, but the same issue exists for other input types inserted in extra_tablenav, as well. E.g, adding a select or an input will also have the extra height.

I think the same logic should be used to ensure that other controls used by core in that context get the compact sizing. The select styling right above can be split between sizing characteristics & positioning characteristics.

I'm not sure that core uses an input in extra_tablenav anywhere, and it's more reasonable that extenders would need to style things not used by core, so it may not be necessary to add that.

Hi @joedolson, Thanks for the suggestion. I have updated to add all the input controls that can be used, but as rightly said, core does not uses all of them and its responsibility of extenders to fix the style if breaks at there end.

For now, I have update the PR to use it for all controls.

Thanks,

@hbhalodia hbhalodia requested a review from joedolson March 25, 2026 09:47
.wp-core-ui .tablenav input[type="week"],
.wp-core-ui .tablenav select {
padding: 0 12px;
/* inherits font size 14px */
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.

Can you share why we need this comment?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It seems unnecessary, given that none of the other related contexts have a similar condition.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Changing my mind; it's helpful, as it gives context for the comment on the line-height calculation.

It comes from the same block of CSS in forms.css, which this duplicates, but adjusting to the compact sizing.

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.

Thanks @joedolson @mukeshpanchal27, Yes I have kept it consistent from the original CSS forms.css.

Copy link
Copy Markdown
Contributor

@joedolson joedolson left a comment

Choose a reason for hiding this comment

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

I think this is good as is; keeping the comment.

.wp-core-ui .tablenav input[type="week"],
.wp-core-ui .tablenav select {
padding: 0 12px;
/* inherits font size 14px */
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It seems unnecessary, given that none of the other related contexts have a similar condition.

.wp-core-ui .tablenav input[type="week"],
.wp-core-ui .tablenav select {
padding: 0 12px;
/* inherits font size 14px */
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
/* inherits font size 14px */

.wp-core-ui .tablenav input[type="week"],
.wp-core-ui .tablenav select {
padding: 0 12px;
/* inherits font size 14px */
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Changing my mind; it's helpful, as it gives context for the comment on the line-height calculation.

It comes from the same block of CSS in forms.css, which this duplicates, but adjusting to the compact sizing.

Copy link
Copy Markdown
Member

@johnbillion johnbillion left a comment

Choose a reason for hiding this comment

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

This fixes the issue in my plugin. Thanks.

@github-actions
Copy link
Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.

SVN changeset: 62115
GitHub commit: 4d3b0b9

This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.

@github-actions github-actions bot closed this Mar 26, 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.

6 participants