TOC active item out of sync

[therepos]

In some instances, the TOC highlighted (active) item is not reflecting the selected anchor (topic) on the page in the current view. I have included a screenshot to illustrate. In the screenshot, user selected the anchor #font. But the TOC does not highlight "Font", instead it highlights the last anchor "Custom CSS". I have also included a sample of this problem at the link below.

https://gothic-modding-community.github.io/gmc/preferences/#font

In my own setup, I am using the following configuration. I've tried other ways including adding additional content or space under the problematic anchor, but this probably should not be the solution. @squidfunk site also spot short topics but the TOC works perfectly in sync with the selected anchor regardless of how short the topic is.

How do we sync the anchor and the TOC active item?

theme:
  name: material
  features:
    - navigation.sections
    - navigation.expand
    - navigation.indexes
    - navigation.tabs
    - navigation.instant
    - navigation.tracking
    - navigation.top
    - content.code.annotate

[kamilkrzyskow]

Hello @therepos,
oh wow someone reporting an issue with GMC 🥹 😂

I'm one of the maintainers there, and this preferences page is created somewhat artificially with placeholders, however it's likely a similar issue as reported in:

• Incorrect secondary nav item is displayed as active despite correct URL hash #8210

So it doesn't look like it's limited to GMC, and the TOC isn't synced to the active #href anchor, but instead it's referenced from the scroll location and therefore it might not highlight the same TOC item.

You could raise a discussion over on GMC Discord and we could try to customize it and override the selected TOC item after the page load, but it's not really a big issue IMHO🤔

[therepos]

Hey @kamilkrzyskow - Thanks for the reply! My intention is purely on troubleshooting the TOC, not reporting issue with GMC. I thought the problem was me but I chanced upon GMC and realised their TOC also encountered similar issue. Appreciate your link to issue #8210!