In 5.8 Metaboxes hide post editor completely

[robertjakobson]

In 5.8, when editing posts, pages or anything else, metaboxes hide the page title and the page content by default every time you open a post for editing. I use page as euphemism for all custom post types.

Expected behaviour: metaboxes are below the page title and page content as is normal
Current behaviour: metaboxes hide the title and the content, which cannot be edited without closing the metaboxes each time you open the page.
The problem: 90% of the time the user wants to edit the title or content, most metaboxes are meant to be edited once and forgotten.

browser: Safari, Mac OS

[Hareesh Pillai]

Hi @robertjakobson! Welcome to Trac and thanks for reporting this.

I see the title and content while editing the page.

Can you confirm if the problem reported above persists while using a default theme (say, Twenty Twenty One) and all plugins disabled?

[robertjakobson]

Yes, with twenty twenty one, it still persists at the browser window size circa 1260x661.

[robertjakobson]

Works fine with Chrome, though. Seems to be a Safari specific issue? I have disabled any Safari extensions that may play around with formatting and it still persists.

[robertjakobson]

Steps to replicate:

1. add plugins such as Yoast or Advanced Custom Fields which have their own metaboxes
2. open up your site in Safari on Mac OS on a smaller desktop screen like a 13 inch Macbook
3. Edit a page or create a new one and you will see the metaboxes of the plugins take over the space meant for the title and content.

[robertjakobson]

@hareesh-pillai hope the video clip I added is enough to get you started tracking this down. I have to go on developing my work.

[sabernhardt]

Similar report: #53865

[ryokuhi]

Hello @robertjakobson,
thank you for taking the time to report this issue. We reviewed it today during the weekly Accessibility Team's bug-scrub.
While this is probably a bug, we don't think it's an accessibility issue and, as such, I'm removing the related focus.
To get a little more traction on this issue, maybe you should open an issue in the ​Gutenberg repository, where the Block Editor development actually takes place.