https://bugs.documentfoundation.org/show_bug.cgi?id=163154

            Bug ID: 163154
           Summary: FILEOPEN DOCX Writer eats bookmark of the first legacy
                    field
           Product: LibreOffice
           Version: 6.2.0.3 release
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Keywords: bibisected, bisected, regression
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
            Blocks: 112969

Created attachment 196686
  --> https://bugs.documentfoundation.org/attachment.cgi?id=196686&action=edit
The example file in Word 2016 and Writer master, with bookmarks visible

This was noticed while looking at the example file bug 79435's attachment
100137 (mentioned in bug 150037)

This docx has 4 legacy text fields and Word creates a bookmark for each of
them.
Writer opens with only 3, making navigation to the first one difficult.

1. Open the above example file, look at the Navigator -> Bookmarks
-> There are 3 bookmarks listed instead of 4

Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 5b54f68599d9a9b6f4d21fd8c0cdac746ea71ecb
CPU threads: 14; OS: Windows 10 X86_64 (10.0 build 19045); UI render: default;
VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: default

Seems to have started in 6.2 with:

https://git.libreoffice.org/core/+/579c0749bef8c980507229439715e72060c1b077%5E%21/#F2

commit  579c0749bef8c980507229439715e72060c1b077        [log]
author  Justin Luth <[email protected]> Tue Oct 09 14:03:37 2018 +0300
committer       Justin Luth <[email protected]>       Fri Oct 12 05:56:01
2018 +0200

tdf120224 writerfilter: consume excess bookmark from fields

Adding CC to: Justin Luth


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=112969
[Bug 112969] [META] DOCX (OOXML) field-related issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to