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.

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

Co-authored-by: karthick-murugan <karthickmurugan@git.wordpress.org>
Co-authored-by: aaronrobertshaw <aaronrobertshaw@git.wordpress.org>
Co-authored-by: hanneslsm <hanneslsm@git.wordpress.org>
Co-authored-by: benniledl <benniledl@git.wordpress.org>

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, @karthick-murugan! 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.

I would love to see this featured merged, as stated in #43247 (comment) already.
I just ran into the issue that I needed this feature again.

My current situation: Building a timeline / step-by-step guide with a dotted border in between the groups.
I can do it by creating a grid or column block and adding a spacer (the spacer is needed otherwise the blocks won't render on the front). However, I also have to wrap it into another group just to apply the border. It'd be easier to maintain when applying the border to the spacer.

This change will end up confusing more users than it helps.

Just because one person has a specific need doesn’t mean it makes sense to implement it in core. WordPress features have to be broadly useful, not just accommodate edge cases for a single user. If we added a setting for every small feature request, we’d end up with tens of thousands of options, making WordPress unusable.

If you need this behavior, the best approach is to use custom CSS. That way, you get exactly what you need without adding unnecessary complexity for everyone else.

This change will end up confusing more users than it helps.

Why do you think so? I also added some arguments about the background for the spacer block to the other discussion but they apply also for the border. Having many groups and divs that do not represent the correct size on the front end is rather confusing and contradicts the idea of a full site WYSIWYG editor.

Just because one person has a specific need doesn’t mean it makes sense to implement it in core. WordPress features have to be broadly useful, not just accommodate edge cases for a single user.

I agree with sentiment in general and there is a lively discussion ongoing in the WordPress community, like https://kraut.press/2024/wordpress-isnt-wordpress-anymore/

If we added a setting for every small feature request, we’d end up with tens of thousands of options, making WordPress unusable.

Here I disagree with you. The block editor has currently a bad user experience because often it's missing options where users would expect them to be. Also, this would rather be a design issue that could be solved (and is for example already partly with the block locking api). If you logic too many options = unusable fully applies than we wouldn't have competitors like Webflow or software like Figma or even Photoshop.
Also, it's not like as if we're talking about many new feature requests in this issue / PR. It's about applying exiting features to an existing block. The corresponding tracking issue outlines clearly that nearly every block already has the features applied to - I don't see a reason why only here, on the spacer block, everything should behave differently. Also look at the code of this PR and you would see that there is no bloat.

If you need this behavior, the best approach is to use custom CSS. That way, you get exactly what you need without adding unnecessary complexity for everyone else.

Again, I don't see any complexity in adding existing appearance tools to the existing (and currently for the spacing block nearly empty) Inspector.
I use plenty of custom CSS for all my themes. It's not an issue for me but I have guided many clients through the editor already who would all expect every block to have the same appearance tools. I think it's ridiculous that one need to write custom CSS in order to create spacing with a border.

@t-hamano - Can I close this PR based on the comments of this PR #66433 (comment) ?

Can I close this PR based on the comments of this PR #66433 (comment) ?

Yeah, let's close it for now. All the same issues in #66433 apply here too.