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

Scrolling is glitchy on Chrome 80 #1177

Closed
mkalam-alami opened this issue Feb 18, 2020 · 4 comments
Closed

Scrolling is glitchy on Chrome 80 #1177

mkalam-alami opened this issue Feb 18, 2020 · 4 comments

Comments

@mkalam-alami
Copy link

mkalam-alami commented Feb 18, 2020

When opening a long spec on Chrome 80 / Windows, scrolling is broken, randomly jumping back to the top of the page. The sidebar also disappears while scrolling. See gif below for an example

Another PC using Chrome 79 did not present the issue. Firefox is OK as well.

  • Reproduction spec: openapi.zip
  • Reproduced using the default ReDoc HTML (latest CDN version, no custom settings)

test2

(NB. I'm using the middle button scrolling for a smooth gif but the bug also occurs when scrolling normally).

@RomanHotsiy
Copy link
Member

Dup of #1170 ?

@Debbus72
Copy link

Don't know if this helps anyone, but on my machine with a long api the navigation-bar glitches when an item gets highlighted that is not completely visible. Tested with multiple sizes of the browser-window and each time an 'offscreen' item should be highlighted the page scrolls back to the top.

Browser: Microsoft Chromium/Edge Version 80.0.361.56 (Official build) (64-bit)
OS: Windows 10 Pro 64bit
ReDoc: 2.0.0-rc.22

@mkalam-alami
Copy link
Author

mkalam-alami commented Feb 20, 2020

@RomanHotsiy I confirm it is fixed with the rc.23. The bug is present in the next release, but not with an explicit rc.23, I'm not sure if that means the bug is back or the CDN is not up-to-date?

CDN link for the lazy:

<script src="https://cdn.jsdelivr.net/npm/redoc@2.0.0-rc.23/bundles/redoc.standalone.js"></script>

@mkalam-alami
Copy link
Author

After checking the JS returned by next it's definitely a CDN issue, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants