The contents pane should 1. scroll to the place corresponding to where the user is viewing 2. open the chapter hierarchy tree when needed 3. indicate the exact location in the tail node with color, and/or arrow, etc. Please look how DjView displays .djvu files, this feature is present there. Applicable to all backends that support chapters.
Thanks for reporting this feature requests :) but please report the three wishes separately, if you report more than one wish in a single issue tracking what is fixed and what is not and asking questions about things quickly becomes a mess.
> please report the three wishes separately This is one request. The 3 items are implementation suggestions how to implement this one item.
Well, i disagree with you so consider this officially ignored by me, i don't want to start a status change war with you, so i'll let you win if that makes you happy.
So you think that one can "3. indicate the exact location in the tail node with color, and/or arrow, etc." without "1. scroll to the place corresponding to where the user is viewing"? I don't see how this can make sense. These 3 items are implementation details, and obviously parts of the same general feature request.
The contents pane already marks the active selected section (there is a large ">" before the actual section name), so (3) can be considered done (observed in Okular 18.08.0). What is missing though is a method to expand all sections above the active section of a page. Consider this TOC: 1. > Chapter A 2. Chapter B A new option could expand sections until the deepest section becomes visible: 1. Chapter A 1.1. Section 1.1.1. > Subsection 2. Chapter B Yuri, does this problem description match yours? Would your issue be addressed if a new "Select current section in table of contents" option was added as a context-menu option for the page/TOC? (My suggestion differs from your proposal as it now requires a manual action. Automatically expanding the TOC as you scroll through the document seems annoying to me.)
*** Bug 431425 has been marked as a duplicate of this bug. ***