Bug 431425

Summary:	Shortcut to expand the TOC tree to the leaf corresponding to the current page
Product:	[Applications] okular	Reporter:	gasdia73 <gasdia73>
Component:	general	Assignee:	Okular developers <okular-devel>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	nate
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description gasdia73 2021-01-11 10:07:27 UTC

I think that having a command that opens the Content tree to reveal the leaf of the page currently displayed would solve many problems that people are having with the TOC at the moment.
It could be a setting to switch on and off, having it on would mean that every time I go to a new page, the tree is expanded to the leaf of the page.
It would be awesome to have an option to shrink/expand all the nodes as well.

Comment 1 Nate Graham 2021-01-11 19:44:38 UTC

> many problems that people are having with the TOC at the moment.
What are those problems? I'm not aware of bug reports on the subject. Can you clarify what problems you're envisioning would be solved by this proposal>

Comment 2 Bug Janitor Service 2021-01-26 04:33:30 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 gasdia73 2021-01-26 11:30:30 UTC

I'm refering to bugs 286776 and 395087, in fact the latter is very similar to what I'm suggesting

*** This bug has been marked as a duplicate of bug 395087 ***