We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
mkdocs
readthedocs
custom_dir
extra_javascript
extra_css
When scrolling upwards the javascript removes the top: 131px element style of the button.
top: 131px
This breaks the positioning when activating navigation.tabs.sticky as the button is partially hidden behind the navigation tabs.
navigation.tabs.sticky
The element style for top: on the back-to-top button should not be removed when scrolling upwards.
top:
Potential cause:
mkdocs-material/src/assets/javascripts/components/top/index.ts
Line 150 in 79c56f5
Build documentation with the following features:
features: - navigation.tabs.sticky - navigation.top
site_name: My Docs theme: name: material features: - navigation.tabs.sticky - navigation.top
The text was updated successfully, but these errors were encountered:
Fixed in f8a19dc – I split the pipeline.
Sorry, something went wrong.
Released as part of 8.0.3
No branches or pull requests
Contribution guidelines
I've found a bug and checked that ...
mkdocs
orreadthedocs
themescustom_dir
,extra_javascript
andextra_css
Description
When scrolling upwards the javascript removes the
top: 131px
element style of the button.This breaks the positioning when activating
navigation.tabs.sticky
as the button is partially hidden behind the navigation tabs.Expected behaviour
The element style for
top:
on the back-to-top button should not be removed when scrolling upwards.Actual behaviour
Potential cause:
mkdocs-material/src/assets/javascripts/components/top/index.ts
Line 150 in 79c56f5
Steps to reproduce
Build documentation with the following features:
Package versions
Configuration
System information
The text was updated successfully, but these errors were encountered: