Show combined TOC on overview page when navigation indexes is enabled

[SoumayaMauthoorMOJ]

When I enable navigation indexes and split the TOC, the TOC for the overview page is still available:

  features:
    - navigation.tabs
    - navigation.tabs.sticky
    - navigation.indexes

However when I enable navigation indexes and merge the TOC with the navigation sidebar I lose the TOC from the overview page:

  features:
    - navigation.tabs
    - navigation.tabs.sticky
    - navigation.indexes 
    - toc.integrate

Is there a way of keeping the TOC from the overview page even when merged with navigation sidebar?

[SoumayaMauthoorMOJ]

Perhaps I should clarify this only affects the overview page:

[squidfunk]

Jup, those features are currently incompatible. It's unclear how we should make them work together 😅

[SoumayaMauthoorMOJ]

Oops I missed the callout :-)

It's a pity they're incompatible but thanks for clarifying!

[ssbarnea]

@squidfunk I know that you documented that toc.integrate and navigation.indexes are incompatible (on only one of them and in a hard to spot way due to the need to click on the bullet), but at the same time I see it possible to enable both without getting any visible errors.

If those features were by design not compatible, we should see a build error, just to avoid accidentally enabling them.

Based on my tests, it seems to be partially working with 9.5.2 version. By partially, I mean that the the index pages cannot have any toc sections displayed. Still, other child pages can have them, only the indexes are affected.

To my this means that one needs to be careful when using these two features combined to keep the indexes brief/small and put the beefy content in child pages. If user needs to scroll when inside the index page, probably you failed to made it small enough.

Am I right about this or I missed some essential side effects?

[squidfunk]

If those features were by design not compatible, we should see a build error, just to avoid accidentally enabling them.

Those are entirely template features – we can't trigger build errors from templates. It works partially, yes, but it's undefined behavior from our side, so it's currently not supported. It might change in the future, but there are currently other priorities.