Table of Contents not scrollable nor in sync with main section

[Usual-Coder]

Description

The "smart Table of Contents" is not scrollable and not always kept in sync with the main section.

How to reproduce

1. Browse a page with enough content to produce a big ToC,
2. Or if you don't have a very long post, to simulate the problem, make your window a little smaller than the ToC height
3. The Table of Contents is not scrollable (you need to scroll the full page)

https://blowfish.page/docs/configuration is a good enough example for this bug

While -basically- you cannot jump to the point you want (you'll have to scroll the full page down, until the point you're interested in), sometimes it makes it even more useless since the smartToc is not in sync with the content (titles / reachable anchors, displayed in the main section, are not even shown in the ToC 🤷)

Expected behavior

Scrollable ToC, really kept in sync with the content.

Screenshots

As stated previously, your own website is sufficient to notice the main bug.

Use the dev tools of your preferred browser to simulate a reasonable window size (like 1680x1050)

Additionally, to demonstrate the problem with inaccessible anchors (while displayed in the main section, it doesn't show, aside, in the ToC), using the first post I'm working on, jump to the #more title/anchor : https://gitlab.pages.usualcoder.com/posts/containerizing-hugo-development/#more

The More... is not showing (is not in sync) in the lateral ToC 🤷

Technical context

Latest versions of everything (browsers, Hugo, Blowfish)

Thanks for considering fixing this 🙇

[nunocoracao]

Not able to reproduce... just tried with the next release of Blowfish and was not able to reproduce the problem in the Configuration page as you mentioned.

[Usual-Coder]

More not displayed/showing in the lateral ToC:

Obviously, the anchor exists (or it wouldn't have been reachable when the corresponding URL was entered ... aka the problem is not coming from the content 😇) ...

... but ... since the lateral ToC is not scrollable or its (sub)levels expandable ... some entries are not accessible (before you reach them or even have to go further than necessary) ... unless you scroll the full page ... which annihilates the main purpose of the ToC 🤷

[Usual-Coder]

Btw, being Product Manager (at Docker or anywhere else), aka "someone experienced in software development processes", your temptation 😇 could be great to close issues as soon as possible (since it's a KPI used in many places 🤐) but, when in the "unable to reproduce" situation, giving the benefit of the doubt is probably not the worst thing to do ... at least for a little while 🤷

Don't get me wrong, I don't pretend to be above making mistakes myself = determining what's a real bug is still your prerogative, of course ... but may I suggest you wait ... let's call it a "reasonable delay" to answer you ... or provide you additional information ?! Avoiding the need to create a new issue (since reopening issues doesn't seem allowed in your repository)

As proved/just answered in another issue, if you add your question label ... you'll get an answer, precisions ... or at least an attempt for a "constructive interaction™" 😉

Just my take / 2 cents ... but hey ... as I said ... I'm a nobody, just the usual coder 😏

Thanks for your time and understanding 🙇

[BluesDriveAmelia]

Having the same issue here with a large ToC, dozen+ headers. Does certainly defeat the point of it.