The docs should scroll when they are longer than the visible webpage
It doesn't scroll in Chrome Version 66.0.3359.139 (Official Build) (64-bit). I tested in incognito to ensure it's not a plugin or something else local to my installation of the browser. Sidebar works fine. Seems to work ok on Safari Version 11.1 (13605.1.33.1.4).
Mac: mac OSX High Sierra 10.13.4 (17E199)
Chrome: Version 66.0.3359.139 (Official Build) (64-bit)
URL: http://docs.readthedocs.io/en/latest/support.html#reporting-issues
URL: http://docs.readthedocs.io/en/latest/alternate_domains.html
I'm not seeing this issue.
Do you have more information?



Reporting Issues
When reporting a bug,
please include as much information as possible that will help us solve this issue.
This includes:
Project name:
URL:
Action taken:
Expected result:
Actual result:
It appears it only happens with an experimental flag enabled in chrome://flags. I made another issue here (which was the original place I saw issue, and was frustrated that I couldn't read the NodeMCU docs.) I think I must have enabled this a while ago, and forgotten about it.
Mac: macOS 10.13.4 (17E202)
Chrome: Version 66.0.3359.139 (Official Build) (64-bit)
It could also be a bug in the latest Chrome, because I never had this issue before. I'm working on MacOS 10.13.4 (17E202) and using the 64-bit version of Chrome 66.0.3359.139.
When I disable the overflow-x rule on the <body> with Chrome Devtools everything works as expected.
My version is same. I also disabled overflow-x and got it working.
Maybe the same issue as https://github.com/rtfd/sphinx_rtd_theme/issues/636? If so, that is a chrome bug, not from rtd.
Can overflow-x: hidden be just removed from CSS?
Removing overflow-x: hidden does also make it possible to scroll for me again.
I just updated to the latest stable 66.0.3359.170 and it seems that the issue reported and marked as resolved landed it's changes in that version. Works with latest stable.
@Fohlen thanks for the update, @konsumer can you try that solution?
@stsewd: As I said, it worked fine when I disabled the experimental chrome features, so I just did that (I don't even remember why I originally enabled those.)
@konsumer can we close this then?
Closing this, as is more a google chrome bug not rtd.
Summing up, in case anyone else stumbles upon this:
Bug filed for Chrome and should be fixed in Chrome 67: https://bugs.chromium.org/p/chromium/issues/detail?id=838494#c10
Disabling 'Experimental Web Platform features' flag at chrome://flags/ seems to fix the issue in Chrome 66.
This still occurs with Experimental Web Platform features enabled on Chrome 67. But disabling Experimental Web Platform features still resolves it.
Most helpful comment
Summing up, in case anyone else stumbles upon this:
Bug filed for Chrome and should be fixed in Chrome 67: https://bugs.chromium.org/p/chromium/issues/detail?id=838494#c10
Disabling 'Experimental Web Platform features' flag at chrome://flags/ seems to fix the issue in Chrome 66.