Verse Block goes outside viewport when it is beside a left or right aligned Image l
Quick summary
Adding a Verse Block beside a left or right-aligned Image Block will make it to go outside the viewport and pushes down blocks below it. Was able to reproduce it on AT and Simple sites in Independent Publisher 2 and Twenty Twenty One.cut
Steps to reproduce
- Add a new post.
- Add an Image block that is not too wide and left-align it.
- Add a Verse block such that it will stay beside the Image block in the editor.
- Add a bunch of dummy paragraphs after these blocks.
- Publish the post and load it on a mobile browser.
- You will notice that the Verse block is outside viewport and blocks after it are pushed down.
What you expected to happen
Verse block should remain in viewport.
What actually happened
Verse block was pushed out of viewport and content after it was pushed down.
Screenshots:
Editor:

Mobile browser:

Context
User report: 5626615-zd-woothemes
Platform (Simple, Atomic, or both?)
Simple, Atomic
Theme-specific issue?
Was able to reproduce in Independent Publisher 2 and Twenty Twenty One
Browser, operating system and other notes
Visible in mobile browser and desktop browsers when they are resized to mobile browser widths.
Reproducibility
Consistent
Severity
All
Available workarounds?
Yes, easy to implement
Workaround details
Removing left or right alignment of the Image block should fix this issue.
Support References
This comment is automatically generated. Please do not edit it.
- [ ] 5626615-zen
- [ ] 5994478-zen
Might be related to this case: https://github.com/Automattic/themes/issues/3892
📌 SCRUBBING : RESULT
- Tested on P2 - Could Not Replicate
- Tested on Simple - Replicated
- Tested on AT - Replicated
- Tested on Self-hosted - Replicated
- Replicable on Core - Yes
📌 ACTIONS
- Marked as Triaged for Quality Squad review
- Added to 'HE Cross-repo Watchlist' project board
Core bug submitted https://github.com/WordPress/gutenberg/issues/44924
A similar problem reported here - 5994478-zd
📌 ACTIONS
Due to the age of this issue, and its dependency on a Core fix, I've downgraded the priority from High to Low to better reflect its status in the larger context of open bugs in this repo.