Yoast metabox covers editor content

[a4jp-com]

• [Yes ] I've read and understood the contribution guidelines.
• [Yes ] I've searched for any related issues and avoided creating a duplicate issue.

Please give us a description of what happened.

There is a huge problem with the Yoast settings area when editing pages. It floats and covers other content!

Please describe what you expected to happen and why.

It should be down the bottom not covering anything. This makes page editing almost impossible at times.

How can we reproduce this behavior?

1. Create a beautiful page on a fresh copy of WordPress with the Twenty Nineteen theme.
2. Search for and activate the Yoast plugin.
3. Try to edit a page with content on it and see how the settings float over the other content at the top T-T.

Safari on iPad OS 13.1 beta 4 doesn't have this problem.

Technical info

• If relevant, which editor is affected (or editors):

• Classic Editor
• [Yes ] Gutenberg
• Classic Editor plugin

• Which browser is affected (or browsers):

• [Version 77.0.3865.75 (Official Build) (64-bit) ] Chrome
• [69.0.1 (64-bit) ] Firefox
• Safari
• Other

Used versions

• WordPress version: Version 5.2.3
• Yoast SEO version: Version 12.1
• Gutenberg plugin version:
• Classic Editor plugin version:
• Relevant plugins in case of a bug:

• Tested with theme: Twenty Nineteen

[Ruud-Mens]

Got the same issue, can't write anything this way. Needs to be fixed asap.
Temporary fix for me is to open the DevTools and set edit-post-layout__metaboxes to display:none. This way you can atleast write.

[Djennez]

Hi @a4jp-com and thank you for your issue. This seems to be related to this issue with Chrome but you're stating you're using the most up-to-date version and you can reproduce this on FireFox as well (please verify that this is indeed the case). Unfortunately, I am not able to reproduce this so it might be a localized issue. Have you checked for any plugin/theme conflicts? Also, can you reproduce this on an empty installation? When the issue is happening, can you check the source of your page for any code that comes before the <!DOCTYPE> tag?

Edit note: changed title to be less dramatic and convey the issue a bit more.

[paddylandau]

This has been fixed with the latest Chrome, version 77.0.3865.90

[Djennez]

This thread will be closed due to inactivity and I believe the root-cause was fixed upstream.

If you have a similar issue, follow this link to open a new bug report.