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
Instant navigation doesn't respect #hash #3274
Comments
Could you please check if the issue also appears with 7.3.6? |
This issue also affects me. |
@kgidarakos in the future, please just use the voting mechanisms on the OP and/or subscribe to the issue. |
In 7.3.6 it's a lot better: the browser window shows page2#anchor at its middle The desired outcome should be: the browser window to show page2#anchor at its top. I.e. 7.3.6 is a whole lot better than 8.0.1, and it's probably acceptable behavior, but maybe not ideal. |
Thanks. There were some changes that might impact instant loading. If you depend on it (e.g. when you have a large search index that you only want to initialize once), the recommendation is to use 7.3.6 for now. |
Fixed in ebcd000. It was a regression introduced in a refactoring done in 8.0.0. |
The fix was just released as part of 8.0.4. |
Contribution guidelines
I've found a bug and checked that ...
mkdocs
orreadthedocs
themescustom_dir
,extra_javascript
andextra_css
Description
When
navigation.instant
is set in mkdocs.yml, if a page1 links to page2#hash, then page2 is indeed loaded, but the #hash part is ignored.Expected behaviour
We should navigate to the #hash header/anchor.
Actual behaviour
We are directed to the start of page2.
Steps to reproduce
Create a page1 that links to page2#anchor.
Package versions
Configuration
System information
The text was updated successfully, but these errors were encountered: