tabbed/alternate broken on mkdocs-material

[casperdcl]

Description

mkdocs-material>=8.1.3 broke #1417 tab linking & scrolling (tabSync, tabOverflow, tabScroll). Note that mkdocs-material==8.1.2 works fine.

Minimal Reproduction

mkdocs config (extra JS & CSS from the docs at https://facelessuser.github.io/pymdown-extensions/extensions/tabbed/#linked-tabs & https://facelessuser.github.io/pymdown-extensions/extensions/tabbed/#alternate-style):

  extra_javascript: [js/extra.js]
  extra_css: [css/extra.css]
  theme:
    name: material
    custom_dir: ../../custom_theme/
  markdown_extensions:
  - pymdownx.superfences
  - pymdownx.tabbed:
      alternate_style: true

Version(s) & System Info

• Python Version: 3.8.12
• Package Version: mkdocs-material>=8.1.3, pymdown-extensions==9.1

[facelessuser]

Unfortunately, I cannot update the docs so that the generalized example will always work with Material (or any other theme for that matter). Material seems to have a very specific way in which they want to handle their content tabs. I provide some general examples that go in a different direction. When Material doubles down in its approach between releases, it may make it harder for the generalized approach I have outlined to keep working.

I am aware that Material changed its style recently and have issued a number of changes in recent commits ensuring this project's approach continues to work, but I have no plans to document as the general working case a hacked up Material specific example.

With that said, these are some of the changes I had to make to work around Material's new animated indicator. You are free to take a look.

• 49dea30
• af74181

I am happy to discuss such cases in the discussion channel, but I do not consider this a bug in our documentation as the examples are sound and are working, but they cannot account for conflicts in various themes that may approach the tab styling differently.

Moved to discussion channel.

[casperdcl]

Yes I think pinning to an earlier version of material is probably best.

[facelessuser]

That is definitely a solution if you aren't keen on ever updating.

For now, I just plan to patch until I get tired and cave to using Material's solution by default. That is obviously my personal decision. I have a certain threshold for maintaining custom solutions. If it takes too much of my time, I'll just use the default 🤷🏻. Currently though, I'm hoping my current solution will persist for quite some time 🤞🏻.