Difficult block insertion in post editor when metabox is displayed

[karl94]

In WordPress 6.6 is difficult to insert new blocks in the post editor when there are plugin showing metaboxes at the bottom of the editor.

Usually the editor leaves some white space below the content, allowing to click in the blank area below to add new blocks.
On WP 6.6 however when a metabox is displayed there's no such space.

This is similar to ​https://github.com/WordPress/gutenberg/issues/63110 except here the issue is the metabox, not the absence of the iframe wrapper.

How to reproduce:

• Load a fresh WP 6.6 install (​https://playground.wordpress.net/?php=8.0&wp=6.6&storage=none&networking=yes)
• Install & activate any plugin that displays a metabox in the post editor (e.g. Yoast SEO)
• Create a new post
• Add enough content to enable scrolling

Expected:
You can scroll past the last block inserted, leaving space to a blank area.

Actual:
There's no blank area available.

[karl94]

Sorry, I attached the wrong screenshot.
The correct one is below

[sabernhardt]

(I removed the first image)

[karl94]

Thanks sabernhardt!

A few more info: I mistakenly reported this as something broken by WordPress 6.6, but after some digging it seems to be always been like this, at least since WP 6.2 (the oldest version I'm able to easily test on Playground).
If the block editor shows metaboxes it won't display the whitespace.

Is there any reason for this behavior?
I think the editor could be more usable if there would be the blank space instead of none.

[sabernhardt]

This discussion would fit better on the Gutenberg repository. I did not notice an existing issue related to inserting blocks with the metabox.
​https://github.com/WordPress/gutenberg/issues?q=is%3Aissue+is%3Aopen+metabox

If you cannot find an issue either, could you open one?
​https://github.com/WordPress/gutenberg/issues/new/choose

[talldanwp]

This looks like the same issue - ​https://github.com/WordPress/gutenberg/issues/63882.

I'll close the trac ticket seeing as editor bugs are usually reported on the gutenberg github repo. Thanks for reporting it though.