Site Editor: Block inserter (+) hovering on content

[rw-ye]

Quick summary

While using the site editor, the block inserter (+) line appears on top of the content, which makes it difficult to add a new block between other blocks.

Similar to the issue here: #63279 however now it is impacting the site editor.

Screen.Recording.2022-06-05.at.2.06.57.pm.mov

Steps to reproduce

1. Enable an FSE-compatible theme.
2. Go to the site editor (Appearance > Editor).
3. Add new content with any block.
4. Hover the cursor at the bottom of the block.

What you expected to happen

The + icon to be displayed at the bottom of the block.

What actually happened

The + icon overlaps the block.

Context

User report: 5271155-zd-woothemes

Simple, Atomic or both?

Simple, Atomic

Theme-specific issue?

FSE Themes

Browser, operating system and other notes

No response

Reproducibility

Consistent

Severity

Some (< 50%)

Available workarounds?

No response

Workaround details

No response

[Jaykame]

Another report here with the same issue happening in Editor: 5278312-zd-woothemes

[cuemarie]

📌 HOUSEKEEPING

• Labels ✅
• Priority ✅
• Replicable on Core - Yes/No

📌 SCRUBBING

• Tested on Simple ✅
• Tested on AT ✅
• Tested on Self-hosted ✅

📌 FINDINGS/SCREENSHOTS/VIDEO

• Could not replicate. Hey folks! On Simple, AT, and Self-hosted test sites, I was not able to replicate the behavior reported above, where the + block inserter appeared hovering over other blocks, rather than between them. Tested on Twenty Twenty Two, Zoologist, and Appleton.
• Also tried opening the sites mentioned above, and could not replicate the issue there either.
• Example recording from AT test site's Site Editor:

Screen.Capture.on.2022-06-14.at.10-00-24.mp4

📌 ACTIONS

• Closed as could not replicate, please reopen this issue if it reoccurs

📌 Message to Author

• @rw-ye and @Jaykame - I was also not able to see this behavior any longer in the user's sites. Both sites have Gutenberg active, which is now on v 13.4, released on June 8 - it's possible that release caught this issue and resolved it already!