Hashlinks from inside docusaurus only work a second time

🐛 Bug Report

Hashlinks only work a second time on big documents when linked from inside docusaurus

Have you read the Contributing Guidelines on issues?

Yes

To Reproduce

1. Create a document with a lot of headers in it
2. Create a document that hyperlinks somewhere around the bottom of the document
3. Click the hyperlink

Expected behavior

Hashlink works as expected and puts you at the right header

Actual Behavior

Hashlink puts you half a page above the right header

(Write what happened. Add screenshots, if applicable.)

Your Environment

• Docusaurus version used: 2.0.0-alpha.58
• Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0): Chrome, production environment (hashlinks don’t work in dev) built with Node.js v12.18.2
• Operating system and version (desktop or mobile): Windows 10 desktop

Reproducible Demo

(Paste the link to an example repo, including a siteConfig.js, and exact instructions to reproduce the issue.) https://github.com/Repulser/Rythm-documentation (should npm run build and serve that since hashlinks don’t work in dev, the big document here is /faq and is linked from /settings#blacklist)

[Repulser]

Hey! Any update on this issue?

[lex111]

Yes, thanks, now I see what the issue is. Indeed, this is related to the loading of images, rather we need to somehow detect that resources was loaded, and only then scroll to the header.