Bug 121099 - FILEOPEN DOC Reference not imported if it precedes bookmarked field
Summary: FILEOPEN DOC Reference not imported if it precedes bookmarked field
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.2.0.0.alpha1+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:doc
Depends on: 120225
Blocks: Fields-Cross-Reference DOC-Forms
  Show dependency treegraph
 
Reported: 2018-11-01 17:07 UTC by Aron Budea
Modified: 2023-07-04 03:13 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Sample DOC (26.50 KB, application/msword)
2018-11-01 17:07 UTC, Aron Budea
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aron Budea 2018-11-01 17:07:21 UTC
Created attachment 146229 [details]
Sample DOC

The attached DOC file contains a Text Form Field (Legacy Form control), which has a bookmark (Text1). It also contains a cross reference (field of type Ref) referencing the bookmark, and it's before the text field this time. The document is protected, only filling in the form is allowed.

- Open attached DOC in Writer.
- Type something in the field.
- Press F9.

=> The reference isn't updated (it's likely lost upon import).

In a build before bug 120225's fix, the referencing field reads "Error: Reference source not found".

Observed using LO 6.2.0.0.alpha1+ (e33424dd887cb1a11a3dba2513ef0f4bf93a6dbe) / Windows 7.
Comment 1 Timur 2019-07-03 12:38:51 UTC
If I understand, in MSO we can right-click after "Referenced content" to update and in LO not. 
DOC should be MSO produced, I guess.
Comment 2 QA Administrators 2021-07-03 04:03:20 UTC Comment hidden (obsolete)
Comment 3 Aron Budea 2021-07-03 07:07:59 UTC
(In reply to Timur from comment #1)
> If I understand, in MSO we can right-click after "Referenced content" to
> update and in LO not. 
> DOC should be MSO produced, I guess.
Indeed, that's are correct, I forgot to add those details.

Bug is still in LO Version: 7.3.0.0.alpha0+ (5e37a1d89dfaa12690841213bce0cb6d05faf90a).
Comment 4 QA Administrators 2023-07-04 03:13:28 UTC
Dear Aron Budea,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug