You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are 2 root causes here - they correspond to the 2 demos above.
Root cause for Demo 1
PR #4797 is the earliest PR that has the bug, so I believe it is the root cause of the regression. Adding back the !hash condition (as shown below) resolves this bug, but I'm not sure if this is the right approach.
Demo 2 is the state before PR #4797 was merged. Certain anchor links still fail. This is due to incorrect anchor link specified on the user side. I will open a PR to resolve this.
The text was updated successfully, but these errors were encountered:
teikjun
added
bug
An error in the Docusaurus core causing instability or issues with its execution
status: needs triage
This issue has not been triaged by maintainers
labels
Jun 20, 2021
🐛 Bug Report
Prerequisites
npm run clear
oryarn clear
command.rm -rf node_modules yarn.lock package-lock.json
and re-installing packages.Description
Anchor links that target headers in other pages are failing. Instead of sending users to the target header, users are sent to the top of the page.
Have you read the Contributing Guidelines on issues?
Yes
Steps to reproduce
getThemePath()
Expected behavior
Expected to go to the target header
Actual behavior
Get sent to the top of the page
Your environment
Reproducible Demo
Demo 1
getThemePath()
linkDemo 2
docusaurus serve
linkRoot Causes
There are 2 root causes here - they correspond to the 2 demos above.
Root cause for Demo 1
PR #4797 is the earliest PR that has the bug, so I believe it is the root cause of the regression. Adding back the
!hash
condition (as shown below) resolves this bug, but I'm not sure if this is the right approach.@lex111 @slorber, could I get your advice on this? 🙏
Root cause for Demo 2
Demo 2 is the state before PR #4797 was merged. Certain anchor links still fail. This is due to incorrect anchor link specified on the user side. I will open a PR to resolve this.
The text was updated successfully, but these errors were encountered: