Skip to content
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

Back-to-top element has no element.style when scrolling up #3283

Closed
5 tasks done
lampensau opened this issue Dec 1, 2021 · 2 comments
Closed
5 tasks done

Back-to-top element has no element.style when scrolling up #3283

lampensau opened this issue Dec 1, 2021 · 2 comments
Labels
bug Issue reports a bug resolved Issue is resolved, yet unreleased if open

Comments

@lampensau
Copy link

Contribution guidelines

I've found a bug and checked that ...

  • ... the problem doesn't occur with the mkdocs or readthedocs themes
  • ... the problem persists when all overrides are removed, i.e. custom_dir, extra_javascript and extra_css
  • ... the documentation does not mention anything about my problem
  • ... there are no open or closed issues that are related to my problem

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

grafik

Potential cause:

Steps to reproduce

Build documentation with the following features:

  features:
    - navigation.tabs.sticky
    - navigation.top

Package versions

  • Python: 3.9.2
  • MkDocs: 1.2.3
  • Material: 8.0.2+insiders.4.1.0

Configuration

site_name: My Docs

theme:
  name: material
  features:
    - navigation.tabs.sticky
    - navigation.top

System information

  • Browser: Chrome, Firefox, Safari
@squidfunk squidfunk added the bug Issue reports a bug label Dec 1, 2021
@squidfunk
Copy link
Owner

squidfunk commented Dec 1, 2021

Fixed in f8a19dc – I split the pipeline.

@squidfunk squidfunk added the resolved Issue is resolved, yet unreleased if open label Dec 1, 2021
@squidfunk
Copy link
Owner

Released as part of 8.0.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue reports a bug resolved Issue is resolved, yet unreleased if open
Projects
None yet
Development

No branches or pull requests

2 participants