Problem with Cover block and its “Change content position” feature

Hi guys,
I am still struggling with this issue. Any of you have an idea how to avoid this blocks width shrinking after setting the Cover block content position on Top Center?

Hi, @kacperludwiczak. I can confirm I am seeing the same:

Interestingly enough, this is not happening when the content of the Cover Block is just a regular paragraph:

I suspect that it might be related to this bug but I am going to take a closer to look to confirm this and to see if I cant suggest a work around.

Ok, I think I found a report describing this issue:

https://github.com/WordPress/gutenberg/issues/50610

I cannot suggest any workaround or provide a date as to when this will be fixed, I would recommend you follow that issue to get new updates.

Hello, @mrfoxtalbot. Thanks for your reply.
I confirm that the situation is different in the case of Paragraph block. I observed that when placing a Paragraph block inside a Cover block, the width of the other blocks contained in the Cover block shrinks to the extent of the text in the Paragraph block – e.g. If the text in a Paragraph fills the entire width of a Cover block, the remaining blocks width do not shrink when repositioned.

Thanks to you I know that the problem lies deeper and is not due to my ignorance. I will keep an eye on this thread until the problem is resolved.

?observed that when placing a Paragraph block inside a Cover block, the width of the other blocks contained in the Cover block shrinks to the extent of the text in the Paragraph block – e.g. If the text in a Paragraph fills the entire width of a Cover block, the remaining blocks width do not shrink when repositioned.

I am having a hard time picturing this and it sounds like it would be a good idea to add it to the GitHub conversation.

Do you think you could share a link to a screenshot or a screen recording to illustrate it?

Thank you!

@mrfoxtalbot, I posted a video in the GitHub conversation.

Thank you for the video @kacperludwiczak, it is very helpful to move the conversation in GitHub at this point. I will mark this thread as resolved for now. Thanks again for reporting this!