Bug 156202 - add the ability to sort bookmarks by position in the document
Summary: add the ability to sort bookmarks by position in the document
Status: RESOLVED DUPLICATE of bug 86395
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.2.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-08 13:15 UTC by kotfantazer
Modified: 2023-07-09 18:06 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kotfantazer 2023-07-08 13:15:57 UTC 
Description:
Now the bookmarks are sorted alphabetically. The option to sort bookmarks by position in the document would be useful.

Actual Results:
the bookmarks are sorted alphabetically.

Expected Results:
the bookmarks are sorted by position in document.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.2.2.2 (x64) / LibreOffice Community
Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: ru-RU
Calc: threaded
Comment 1 kotfantazer 2023-07-08 13:21:15 UTC 
Sorry I wrote Expected Results wrong.

Expected Results:
We have an option to sort the bookmarks by position in document.
Comment 2 Roman Kuznetsov 2023-07-08 16:58:41 UTC 
Do you mean Navigator or Bookmarks dialog?

Anyway I see the opportunity to sort bookmarks in the both place in current development version (future 24.2)

Please try to update your LibreOffice to 7.5 for example
Comment 3 Stéphane Guillou (stragu) 2023-07-09 18:06:34 UTC 
Up to 7.3, the document order could be wrong. Since 7.4, we have the choice between both options.
Marking as duplicate of bug 86395, but please set back to unconfirmed if you disagree, can reproduce in 7.5.4 and can provide more information about the issue.

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