The latest posts block doesn't render the post blocks properly when displaying the post content

[renatho]

Description

When we add the Latest Blocks to a page, activate the "Post content" and "Full post", I would expect to have the full post rendered properly as it works in the page, but it doesn't parse the blocks properly.

I noticed this related issue, and this state of this PR (currently open) seems to fix the issue on the frontend. But in the editor it continues broken.

It was originally reported in Automattic/wp-calypso#88833

Step-by-step reproduction instructions

1. Add a gallery block to a post with at least 2 images.
2. Create a new page.
3. Add the "Latest Posts" block.
4. In the sidebar settings, check "Post content" and "Full post".
5. Check that the gallery doesn't have the images side by side as the original post.
6. Check the editor, and see that the same happens.

It's not related specifically to the Gallery block. It also happens with other blocks.

Screenshots, screen recording, code snippet

The post:

The page in the editor with the Latest Posts block, and its settings:

The page in the frontend:

The page in the frontend applying this commit (in the editor it continued broken):

Environment info

• WordPress: 6.7.2
• Gutenberg: 20.4.0
• Theme: Twenty Twenty-Four
• Browser: Chrome
• Device: Desktop Mac OS

Please confirm that you have searched existing issues in the repo.

• Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

• Yes

Please confirm which theme type you used for testing.

• Block
• Classic
• Hybrid (e.g. classic with theme.json)
• Not sure

[code-with-mehedi]

@renatho Thanks for creating this ticket. I have checked the mentioned PR and am trying to reproduce the issue on my end.

[JorgeVilchez95]

Hi! I just created a PR that fixes this CSS bug.

Sorry @code-with-mehedi , I started working on this without saying before that I'm going to do it

[carolinan]

Also probably a duplicate of #61477

[Mamaduka]

@renatho, can you confirm if it's a duplicate of #61477? There's no need to have two issues for the same bug.

[renatho]

@carolinan and @Mamaduka, thank you for the ping and for the reference of the other issue! It really seems to be a duplicate one. So closing this one in favor of #61477.