Merged
Conversation
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
github-actions
bot
added
the
First-time Contributor
|
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @jasmussen! In case you missed it, we'd love to have you join us in our Slack community. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
Contributor
Author
|
I would like to update the icons as well. I will provide some alternatives here in a bit, but one thing I think we should do, is use the same icon that Accordion uses for the content, extract that and add it to the icon library, and reuse it here for "tab content": The difference between two blocks that could arguably be mostly the same isn't worth maintaining, IMO: 
|
Contributor
Author
|
Also potentially a followup: we don't do this for any other block: I don't think we should be doing that here: building in flex/flow/constrained/grid into the Tab Content block itself. Accordion, Navigation Overlay, and other similar containers allow you to insert any container block you want, Group, Stack, Row, Grid, and thus choose which type of layout you have. IMO that should be how you choose the layout, otherwise this will be a bespoke and used-only-once interface for choosing block layout, that will be prone to code drift as those other container blocks evolve. As a segmented control, it's also likely to translate poorly to longer languages. |
jasmussen
added
[Type] Enhancement
Contributor
Author
|
Also, in addition to unifying to use the same icon between Tab Panel and Accordion Panel, we should unify the titles: 
Right now it's called Tab Panels (plural). @mikachan what do you think? I will need to change this code: Better do this now before beta, yes? |
|
Size Change: -116 B (0%) Total Size: 2.98 MB
ℹ️ View Unchanged
|
Contributor
Author
|
Here are the new icons I'm proposing. Probably can follow up with these separately, but sharing here to keep the discussion focused: 
Edit: typo in the pic above, it shouldn't say "form input". The concepts were good, so the changes are mostly minor:
SVGs. Tabs: Tabs-menu: Tab: Panel-contents: |
Merged
t-hamano
approved these changes
Feb 3, 2026
Contributor
t-hamano
left a comment
t-hamano
left a comment
There was a problem hiding this comment.
Thanks for working on this! I think this block deserves further polish, but for now I think it's okay to ship the PR as is.
I don't think we should be doing that here: building in flex/flow/constrained/grid into the Tab Content block itself.
I agree with this. Additionally, the following points can also be improved.
- Remove the Label UI. This is because the tab label can be edited directly by clicking the tab itself. Text fields cannot express HTML tags.
- Refactor the panel by using the
ToolsPanel.
Ultimately, the UI should be simplified as follows. Of course, this can be addressed in a follow-up PR rather than in this one.
Comment on lines
94
to
97
| label={ __( 'Remove the current tab' ) } | ||
| onClick={ removeTab } | ||
| showTooltip | ||
| text={ __( 'Remove Tab' ) } | ||
| text={ __( 'Remove tab' ) } |
Contributor
There was a problem hiding this comment.
Can we remove the unnecessary label and showTooltip prop?
Co-authored-by: Aki Hamano <54422211+t-hamano@users.noreply.github.com>
Member
|
Thanks so much for working on this, @jasmussen!
Yes, agreed, we should rename "Tab Panels" to "Tab Panel". That change can be made as part of this PR or a follow-up, either is fine. And yes, best to do this before Beta. Also happy for this PR to land as it is, and we can address the other issues mentioned in follow-ups. Once it's landed, we can list the remaining issues on the main tracking issue: #73230. |
Contributor
Author
|
Thanks for the feedback, I believe I've addressed the label feedback, and the rename. But because the rename is kind of a big thing, I would appreciate a re-testing of this branch to ensure everything is caught correctly. It's a breaking change for existing tabs (all the more important to do it soon). |
mikachan
reviewed
Feb 3, 2026
Member
mikachan
left a comment
mikachan
left a comment
There was a problem hiding this comment.
This is testing well for me:
But we should also probably rename the block's directory and the other places in the codebase where it's referenced as "tab panels" (I can push a commit for that if you prefer.)
Contributor
Author
|
Feel free to push a commit, thank you! I have to briefly move on to another thing. |
Contributor
Author
|
Actually, went ahead with the rename, should be fixed, but would again appreciate a quick check, thank you! |
Member
|
I spotted some other "tab panels" references, so I went ahead and updated these as well. It'd probably be good to ensure these changes work for you as well, but otherwise, this is testing well for me! |
Contributor
|
I made some small changes too, but overall I think it's good. |
|
Flaky tests detected in 8e7ea34. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/21662515678
|
Contributor
Author
|
Merged. Thanks all. I will see about the followups now, I think I'll start with opening an issue that captures icons and unfinished thoughts from this thread, then dive into code if time permits. |
Contributor
Author
|
Created #75195 as a followup. |
MaggieCabrera
pushed a commit
that referenced
this pull request
Feb 10, 2026
* Tabs block: Polish * Update packages/block-library/src/tab/add-tab-toolbar-control.js Co-authored-by: Aki Hamano <54422211+t-hamano@users.noreply.github.com> * Remove label. * Rename to "Tab-Panel" * Remove showTooltip prop. * Rename tab-panels folder. * Rename other tab panels refs * Additional renaming --------- Co-authored-by: jasmussen <joen@git.wordpress.org> Co-authored-by: mikachan <mikachan@git.wordpress.org> Co-authored-by: t-hamano <wildworks@git.wordpress.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Followup to #69789. Polishes the new Tabs block.
Why?
The block is very functional and nice, but doesn't follow best practices in all cases. This PR polishes up a few of the pieces.
How?
Before:
Title Case for many labels and items, toggle instead of checkbox, a typographic widow, few small pieces. After:
Testing Instructions
Insert the Tabs block, explore.