Bug 52113 - Navigator should show the Hyperlinks embedded in TOC separately
Summary: Navigator should show the Hyperlinks embedded in TOC separately
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) rc
Hardware: Other All
: low enhancement
Assignee: Not Assigned
Depends on:
Blocks: Navigator
  Show dependency treegraph
Reported: 2012-07-15 11:03 UTC by narayanaras
Modified: 2017-06-26 18:40 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description narayanaras 2012-07-15 11:03:37 UTC
The very purpose of the Navigator is to navigate in the document. 

The "hyperlinks" section in the Navigator is supposed to give you all manually inserted hyperlinks, so that you can check out the "from-to" relationships.

However, this purpose is defeated because the Navigator mixes up a large number of hyperlinks from the TOC to the manually created hyperlinks.

There is a difference between hyperlinks inserted in TOC and hyperlinks inserted in the rest of the document:
* A typical TOC will be built from all Headings 1-3 of the document.
  These headings are already available from the "Headings" section of the Navigator.
* In the rest of the document, hyperlinks are used for cross-referencing. They are NOT related to the structure of the document, and these hyperlinks are not available anywhere else.

Desired solution:

Please provide a separate node for hyperlinks belonging to a TOC.
That would allow the user to focus on the other non-TOC hyperlinks.
Comment 1 Joel Madero 2012-12-12 16:45:42 UTC
Changed wording from must to should as it's less aggressive and this is an opinion bug.

Marking as an enhancement request, low priority.


Enhancement: LibreOffice behaves as it's expected to behave, this enhancement request could make LibO more functional for some users but isn't a bug.

Low: Navigator in general is not a very much used module of LibO, only more advanced users really even know about it. 

Don't think low priority means it won't be looked at by a developer, it simply is saying "compared to features that virtually every user uses, this one is lower in relative terms"