Bug 121067 - FILESAVE DOC Bookmark not saved when updating field with reference (check in Word after RT)
Summary: FILESAVE DOC Bookmark not saved when updating field with reference (check in ...
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-10-30 19:04 UTC by Aron Budea
Modified: 2023-04-16 03:24 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Sample DOC (26.50 KB, application/msword)
2018-10-30 19:04 UTC, Aron Budea
Details
Roundtripped, buggy DOC (10.00 KB, application/msword)
2018-10-30 19:05 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-10-30 19:04:33 UTC
Created attachment 146176 [details]
Sample DOC

This is a follow-up bug report after bug 120225. I modified the sample slightly to avoid bug 108772 in Word after RT.

- In Writer, fill the text field, and press F9.
- Save and close file.
- Open it in Word, switch to edit mode, disable protection (no password needed), and double-click field.

=> Among settings, Bookmark field is empty (should be Text1 for this doc).

Alternatively, in Word simply change the field content, and go to Print mode and type something else in the field. In this case the field "disappears" (ie. the text isn't entered in a field anymore), and not just changes.

Observed using LO 6.2 alpha1 / Windows 7.
Comment 1 Aron Budea 2018-10-30 19:05:42 UTC
Created attachment 146177 [details]
Roundtripped, buggy DOC
Comment 2 QA Administrators 2021-04-15 03:43:24 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2023-04-16 03:24:41 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