toc.integrate doesn't seem to work for second-level menus

[DeNelo]

I have enabled toc.integrate in mkdocs.yml, and it works nicely.
I also have navigation.tabs enabled.
However, when using second-level (or is it third-level?) menus, then any headings in my index.md are shown in an oddly placed local menu, not integrated into the main TOC. This excerpt:

nav:
  - Architecture:
      - platform/doc/architecture/platformArchMenu.md
      - System configuration, General:
          - platform/doc/architecture/deploy/index.md
          - Authentication: platform/doc/architecture/deploy/authConfiguration.md
          - Batches: platform/doc/solution/batches/batchConfiguration.md

Here, the headings in platform/doc/architecture/deploy/index.md are not integrated into the main TOC.

I tried to ChapGPT this, but it gave up. My index.md is formatted correctly, not jumping any heading levels. I tried making sure the heading text was identical with the TOC (that is, "System configuration, General").

Any ideas as to why the local toc is not integrated into the main TOC?

[mocdaniel]

Some toc/navigation settings don't play nice when combined, would you mind sharing the mkdocs.yaml you're observing this behavior with?

Make sure to redact any sensible information, please.

[alexvoss]

Even better, create a minimal reproduction so we can see a minimal example. Often times, creating the reproduction already helps solve the problem, esp. if the issue is caused by a customization and turns out not to be reproducible without it.

[DeNelo]

OK, I made a minimal reproduction. As I feared, the problem went away :) - almost: I don't think the documentation says anything about the local (on this page) menu going away if the navigation.indexes AND toc.integrate are active. See for yourselves - clicking "Business processes" (which is index.md) does not show the level 2 and 3 headings within the main TOC - they go away completely.
And actually, that would be preferable in my situation, rather than having the local toc appear in a funny location below the main toc.

Here is my reproduction: 9.6.15-toc-integrate.zip

[alexvoss]

Looking at the discussions, this was discussed before in #5805. Not sure if there is a solution to this as the two options seem (to my mind at least) logically incompatible and any attempt to reconcile them would probably cause more problems than it solves.

[DeNelo]

You are right, it has been discussed - I couldn't find it.
Also, I'm loath to say, I have a custom thing in a template which may cause the local toc to show anyway. So I will mark yours as an answer!

[alexvoss]

Would you mind sharing a screenshot or point us to the documentation so we can see this? It is not inconceivable that this could be supported in the future, so knowing what the options are for integrating the ToC of an index page would be good.

I think for now it is the right approach recommend avoiding the combination of the two options but it would be good to document your solution.

[DeNelo]

Sure, @alexvoss, here is a screenshot!

"On this page" is placed below the nav toc. I wish it would have been merged into the nav toc instead.
Mind you, I added something in my main.html, which now looks a bit strange:

{% block site_nav %}
<div class="md-sidebar md-sidebar--primary" data-md-component="sidebar" data-md-type="navigation" {{hidden}} >
<div class="md-sidebar__scrollwrap">
    <div class="md-sidebar__inner">
    {% include "partials/nav.html" %}
    {% include "partials/toc.html" %}
    </div>
</div>
</div>
{% if "toc.integrate" not in features %}
  <div class="md-sidebar md-sidebar--secondary" data-md-component="sidebar" data-md-type="toc" {{hidden}} >
    <div class="md-sidebar__scrollwrap">
      <div class="md-sidebar__inner">
        {% include "partials/toc.html" %}
      </div>
    </div>
  </div>
{% endif %}
{% endblock %}

-coupled with a javascript that hides the second instance of a nav element:

function removeSecondSecondary(){
    if(document.querySelector('ul .md-nav--secondary')) {
        document.querySelector('.md-nav--secondary:nth-child(2)').style.display = 'none';
    }
}

So - there's quite a lot of moving parts! What I wanted to achieve was to put the secondary, local toc on the left always (to save screen real estate). We have so many pages that the nav element doesn't cover 5% of them, so the left-hand menu is usually empty. But if it isn't, we want to integrate the local toc into the main toc.
Not sure if I'm making myself clear, but ask again!