Make current page section detection resilient to sticky elements above header #664
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
In https://github.com/Qiskit/qiskit_sphinx_theme, we have to add a custom header to the top of the site, like this:
This naturally breaks the detection of what the current scroll section is in the page table of contents, as it does not account for elements above the header:
Solution
This is easily fixed by also including the
header.top
in the offset.In base Furo,
header.top
is 0, so this change has no impact. I suspected this PR might be necessary for setting up banners, but because banners are not sticky,header.top
ends up going back to 0 even with a banner when scrolling down.While it has no impact on base Furo, it makes customization of Furo much easier. It's particularly complicated to tweak the JS code because it's being built by Webpack.