Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Required label: Any label starting with [Type].
• Labels found: [Package] Block library, [Block] Verse, First-time Contributor, [Block] Search.

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Required label: Any label starting with [Type].
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

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: @EldarAgalarov.

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

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: EldarAgalarov.

Co-authored-by: Shekhar0109 <[email protected]>
Co-authored-by: SirLouen <[email protected]>
Co-authored-by: t-hamano <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @Shekhar0109! 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.

@t-hamano I'm not sure if this approach is mutually exclusive with #74723

What do you say?

#74722 and #74723 are not exclusive; they solve different problems.

This PR resolves overflow when the left or right padding is applied to a block.

Here is an example of the Verse block:

trunk	This PR

However, since the Search block doesn't support padding in the first place, box-sizing doesn't appear to make any visual changes.

@Shekhar0109, why did you add box-sizing to the Search block as well as the Verse block?

This PR resolves overflow when the left or right padding is applied to a block.

👌 I saw it clearer after reading through #43465 I did not understand at first the intention of #74717 and then I noticed that #74723 was also a good addition.

@t-hamano Thanks!

I added box-sizing: border-box for Search too because the original issue (#74717) mentioned both Verse + Search having max-width/overflow issues, and the fix is basically the same at the wrapper level.

That said, if Search doesn’t actually show any change right now (since it doesn’t support padding), I’m totally fine dropping the Search part and keeping the PR only for Verse. Just let me know what you prefer and I’ll update the PR.

@Shekhar0109 Can we focus on the Verse block only in this PR? See #74717 (comment) for the reason.

It would also be great if you could update the PR title and description.

@t-hamano Sure! I’ll update this PR to focus on the Verse block only and adjust the PR title/description accordingly. Thanks for the guidance.

@t-hamano Quick update: I’ve reverted the Search change, so this PR is Verse-only now, and updated the title/description accordingly.