Revert "[docs] Fix layout regression"

[eps1lon]

Reverts #27266 which was accidentally merged. There was no reproduction provided and we don't merge "fixes" that are unconfirmed.

Broke layout on

• Chrome Version 91.0.4472.114 (Official Build) (64-bit) Ubuntu 20.04
• Firefox Version 89.0.2 Ubuntu 20.04
• Chrome Version 91.0.4472.114 (Official Build) (64-bit) macOS Catalina
• Safari Version 14.1.1 (Official Build) (64-bit) macOS Catalina

[mui-pr-bot]

No bundle size changes (experimental)

Generated by 🚫 dangerJS against 929219c

[oliviertassinari]

@eps1lon Nice spotted, I can reproduce the issue on the API pages. 👍 for fixing it. If we revert this one, I propose, we revert the issue from the root: #27138. Otherwise, we can work on a solution that cover these two constraints.

[eps1lon]

We can revert #27138 once we have identified the issue.

[eps1lon]

@eps1lon Nice spotted, I can reproduce the issue on the API pages.

This reproduces on /api, /components, /guides etc. Including the page that you claimed was fixed.

[oliviertassinari]

The PR leads to this issue:

1. Open https://deploy-preview-27269--material-ui.netlify.app/guides/migration-v4/ on any browsers, resize the screen to be 1400px wide.
2. See that the TOC is partially visible

[oliviertassinari]

I might have figured out why you couldn't reproduce my bug report, and why I couldn't understand what information was missing. It seems that it's about the screen width. Do you have a large display by any chance? Mine is small. I have updated #27269 (comment) accordingly.

If we look at the source of my screenshot it's 2724 pixels wide, with a x2 pixel ratio, my viewport is 1362px. Does it help?

[eps1lon]

We can discuss the repro of the your bug somewhere else. The screen size is not the problem. I've resized all the way from 1px to 2510px and could not reproduce it. You're missing some more information about your environment. Might be pixel density.

[eps1lon]

It's especially confusing since now you report a different issue. I can only encourage you to go through the bug report steps since you seem to be unable to write a coherent bug report.