I add the class inner-container or wp-block-group__inner-container to the blocks, but nothing changes

@Ooker if you added it via the sidebar then that was not the solution

and Caroline Poena addresses that very question in the ticket on core Trac

your custom block doesn't have vertical paragraph spacing because it doesn't add any

imo you should avoid using that block until the issues are resolved, and imo you do not need that block

about 3 or 4 questions, several github issues and trac tickets are all because you want a group block with rounded corners

rather than adding rounded corners, you've gone to a 3rd party block that has spacing issues and gone on a wild goose chase trying to fix it

when all along 3 lines of CSS in the additional CSS box of the customizer would have gotten you what you wanted

and I suspect, despite all of this, you still haven't opened up a feature request on the gutenberg repo to add rounded corners to group blocks :)

also, I added inner-container to the ugb-container__content-wrapper div and it fixed the spacing, this is a problem that can be easily fixed in the stackable plugin, and it isn't something you can fix by changing something in the user interface

@TomJNowell yes I know that. However I already used that block in various posts, so it would be more tiring to replace all existing one than figuring out how to fix it

plus that it also affects other custom blocks as well, and it seems to be a part of a deeper problem.

If you check this test post, where I gather all the bugs in one place, you will see that the paragraph 2 in the native group isn't indented as expected, while the paragraph 2 in the custom block is indented.

you can continue the conversation in Trac from here. It's the most updated

it sounds like you just need to wait for an update to the twentytwentyone theme, and test Carolines changes

in which case you need to grab a copy of the dev version of twentytwentyone and test if it fixes the problem

if you don't know how though, you need to say in the ticket or everybody will assume you know how

I would also keep in mind that you are in danger of derailing your own ticket by trying to make it a holistic ticket that covers all the problems you're facing

rather than an ultra specific ticket that can be described, patched, and resolved

instead of 1 ticket for all the vertical alignment issues, create an individual ticket for each separate problem

that way fixing problem 1 isn't blocked by problem 2

e.g. spacing issues in widgets aren't blocked by spacing issues with inner blocks

otherwise it just becomes complicated, you now have someone trying to do a discussion and asking questions about inner blocks in a ticket that reports widget spacing issues

and getting all the information means following the journey you made too, I had to click around to collect all the information, some of your posts mention the Trac ticket, but not the github issue, and some have links to your post, but others don't

@TomJNowell Thanks. At that time I thought the vertical margin issue for widget and the vertical margin issue for the entry content is the same, and that issue is also be the same with the left margin issue. And you know, we need to tackle the root of the problem. Now I figure out that they are not.

Also I'm sorry for you to have to click around to have full picture. I guess we can concentrate at the Trac ticket now.

thank you for your time in helping me. I appreciate it

no problem, just make sure things don't get sidetracked, it'd be good to have all of this resolved for the wider ecosystem and having everything neat and tidy helps everyone