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

Weird Firefox Content Tab Button Behavior #3977

Closed
5 tasks done
facelessuser opened this issue Jun 2, 2022 · 3 comments
Closed
5 tasks done

Weird Firefox Content Tab Button Behavior #3977

facelessuser opened this issue Jun 2, 2022 · 3 comments
Labels
bug Issue reports a bug resolved Issue is resolved, yet unreleased if open

Comments

@facelessuser
Copy link
Contributor

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 using content tabs, and the overflow indicator buttons appear, Firefox will keep scrolling to the left when you scroll all the way to the right.

This occurs in the default Material Docs:

tabbed

Expected behaviour

Firefox should not cause tabs to scroll back to the start when scrolled to the end.

Actual behaviour

Firefox causes scroll to the start when scrolling to the end.

Steps to reproduce

See GIF above

Package versions

  • Python: 3.10
  • MkDocs: NA
  • Material: 8.3.0

Configuration

See the above GIF. Can be replicated in current Material Docs

System information

  • Operating system: macOS
  • Browser: Firefox
@squidfunk squidfunk added the bug Issue reports a bug label Jun 3, 2022
@squidfunk
Copy link
Owner

Fixed in 35210f5. I disabled scroll snapping for content tabs, as I don't want to get into fighting browser bugs here. This makes scrolling seamless, and when a tab is clicked, it is brought into view anyway, so no real need for scroll snapping.

@squidfunk squidfunk added the resolved Issue is resolved, yet unreleased if open label Jun 4, 2022
@squidfunk
Copy link
Owner

I fixed another bug in c4cb6b4 where the scroll offset was not correctly computed when tabs are brought into view.

@squidfunk
Copy link
Owner

Released as part of 8.3.1.

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