Slugs for content tab anchor links that use headers in slug

[chipsenkbeil]

Problem

When clicking on the tabs from content tabs that have the same names, I get links like these:

• example.com/#about
• example.com/#value
• example.com/#about_1
• example.com/#value_1

What I'd really like is to have the headers factor into the slug:

• example.com/#log_file-about
• example.com/#log_file-value
• example.com/#log_level-about
• example.com/#log_level-value

Is there any way to achieve this today? I was trying to figure out if I could write my own python function, but I couldn't easily determine that nor could I determine if there was a way to get the header(s) preceding a content tab.

Yaml Config

My mkdocs.yml has readable slugs:

markdown_extensions:
  - pymdownx.superfences
  - pymdownx.tabbed:
      alternate_style: true 
      slugify: !!python/object/apply:pymdownx.slugs.slugify
        kwds:
          case: lower

Markdown

My markdown is using content tabs with a header to delineate:

#### log_file

=== "About"

    Specifies an alternative path to use when logging information while the
    client is running.

=== "Value"

    String representing the path to the file.

#### log_level

=== "About"

    Specifies the log level used when logging information while the client
    is running.

=== "Value"

    String representing the level. **[default: info]**
    Choices are off, error, warn, info, debug, trace.

[squidfunk]

I don't think it's currently possible. No, wait, I think it is possible by supplying your own slug function. I'm not sure, however, since I've never did this before. I think it is a good idea to raise this question to the maintainers of Python Markdown Extensions 😊

[chipsenkbeil]

Sent over a feature idea to them: facelessuser/pymdown-extensions#2098

[facelessuser]

This feature will be added to the next version of Pymdown Extensions. It will be supported under the legacy format:

=== "title"
    ...

And the new block format:

/// tab | title
...
///