Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IE11: the meta boxes area overlays the post #13503

Closed
afercia opened this issue Jan 25, 2019 · 9 comments
Closed

IE11: the meta boxes area overlays the post #13503

afercia opened this issue Jan 25, 2019 · 9 comments
Labels
Browser Issues Issues or PRs that are related to browser specific problems CSS Styling Related to editor and front end styles, CSS-specific issues. [Type] Bug An existing feature does not function as intended [Type] Regression Related to a regression in the latest release

Comments

@afercia
Copy link
Contributor

afercia commented Jan 25, 2019

Previously #5503.

See also #13328, #11378, and #12455.

Tested with:

  • Windows 10
  • Internet Explorer 11
  • WordPress trunk (5.1)
  • Yoast SEO 9.5

Note: I've used the JS snippet from #12455 and the browser is running in Standards mode.

Depending on the length of the post content, the meta boxes area is misplaced: it doesn't stay at the bottom of the page. This is more noticeable when collapsing the meta boxes area, see screenshot below:

  • make sure the post has some lengthy content
  • collapse the meta box area
  • scroll the page

screenshot 179

@afercia afercia added [Type] Bug An existing feature does not function as intended Browser Issues Issues or PRs that are related to browser specific problems [Type] Regression Related to a regression in the latest release labels Jan 25, 2019
@friendofpa
Copy link

friendofpa commented May 23, 2019

I can confirm that this issue is still persisting. If the post body exceeds the desired height from text length the post body element is overflowing through the post meta box elements. As seen in image below:

Capture

  • Yoast SEO, Custom Fields Plugins
  • Chrome: (Windows 10) Version 74.0.3729.157

@LordSimal
Copy link

I got the same problem with the current Chrome Version 77 but not with Version 76 or Firefox 69 or Safari 12.1.2

I already created a Chrome Issues since it seems to be a render issue.

See https://wordpress.org/support/topic/yoast-12-0-breaks-gutenberg/ for the details

image

@LordSimal
Copy link

FYI: My Problem is actually #17406 which already includes a temporary fix.

@kajcula
Copy link

kajcula commented Nov 6, 2019

In CSS display for .edit-post-layout__content element is set to flex but I think that it isn't necessary. All Gutenberg blocks are stacked one below the other inside this edit-post-layout__content, so this should fix the issue: Set display to block for admin styles:

.edit-post-layout__content {
  display: block;
}

@tellthemachines tellthemachines added the CSS Styling Related to editor and front end styles, CSS-specific issues. label Jun 30, 2020
@paaljoachim
Copy link
Contributor

paaljoachim commented Feb 21, 2021

Is this still an issue? @tellthemachines
How can we move the issue forward?

@LordSimal
Copy link

In the current state I am not able to reproduce it (Yoast 15.8, WP 5.6.1)
image

But as said above my resolution was found in #17406 which basically was a chrome bug, not a gutenberg bug

@paaljoachim
Copy link
Contributor

paaljoachim commented Feb 21, 2021

I will go ahead and close.
If I am mistaken then please reopen the issue.

@LordSimal
Copy link

Besides the fact that the current yoast doesn't even work anymore with IE11
image

@paaljoachim
Copy link
Contributor

Microsoft is ending support for IE 11.
Which means I believe we can also close all IE 11 issues in Gutenberg.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Browser Issues Issues or PRs that are related to browser specific problems CSS Styling Related to editor and front end styles, CSS-specific issues. [Type] Bug An existing feature does not function as intended [Type] Regression Related to a regression in the latest release
Projects
None yet
Development

No branches or pull requests

6 participants